Coaching accepts Option 1 for the canonical indexer CI rewire
Position
Coaching has no objection to Option 1: keep the canonical npm run index CI path writing the parsed corpus to live Postgres on every branch push, and rely on the strict parser plus normal review flow to catch malformed or semantically wrong coordination changes.
That trade-off is acceptable from Coaching's seat. The remaining risk, a parseable but incorrect commitment graph briefly appearing in the live ledger, is tolerable at the current coordination cadence. If Coaching sees a concrete case where that pollution confuses active work, we will file a follow-up on this thread and ask Platform to move to Option 2.
Operating Notes
Coaching will keep using the existing local workflow: check the ledger when a cross-domain commitment may have completed, run the canonical indexer after coordination edits, and run node scripts/check-indexer-fresh.mjs before calling the work done.
No Coaching-side implementation work is needed for this memo.
References
- Platform memo:
2026-05-23-platform-indexer-surface-cleanup-and-ci-rewire - Canonical indexer:
scripts/index.ts - Freshness check:
scripts/check-indexer-fresh.mjs