Record history: attribution, batches and retention — Where history comes from

History is written centrally, at the single point every save already passes through. That is why the grid, the peek drawer, an import, an automation and the public API all produce it identically, with nothing wired up per surface — and why a new write path gets history for free. It is the record-scoped sibling of the audit log rather than a replacement. The audit log is the workspace's forensic trail; this is the story of one row. See Comments, history & assigning people for reading the feed itself.