Accountability README

The accountability module turns the platform thesis into receipts. Successful editor workflow mutations become append-only editorial_changes rows, the current editor sees those rows in the recent-changes panel, and analysts inspect the same trail in the Observable change log.

The source README lives at tutorial/accountability/README.md. It explains why accountability has its own role-named module instead of being buried in the editor or editorial directories, and it documents the honest scope boundary: direct API writes bypass the audit because the audit is evidence of the editor workflow, not every possible warehouse mutation.

That is the operational proof of ADR-0004: editorial accountability is a platform-layer concern. The lightweight observability shape stays aligned with the analytical surface first framed in ADR-0021 and productionised with Observable in ADR-0025. Together with the assistant operations dashboard, this keeps the observability layer table-backed and inspectable without adding a heavy ops stack.