The same rating key can mean a marketplace average or someone's bad afternoon. Your ingestion job accepts the number, and your app summary suddenly sounds like an angry review.
Lab note 111: we wanted to pin down where a retrieval pipeline should separate app-level evidence from individual testimony.
The catch comes early: the example below is synthetic. It demonstrates an ingestion boundary, not measured answer quality. Separating evidence also won't make a capped collection of reviews representative.
The collision fits in valid JSON
Our app-market Actor can attach reviews to app records and also emit standalone review records.
The Actor's recordType determines whether rating means an app average from 0 to 5 or an individual review score from 1 to 5.
Example: these synthetic records deliberately share an appId while making different claims.
rows = [ { "recordType" : "app" , "appId" : "example-app" , "name" : "Example app" , "rating" : 4.5 , "reviewCount" : 10 , "description" : "Example inventory…