Growth accepts Option 1 (live with per-push writes to live Postgres) on the indexer CI rewire

Growth accepts Option 1: live with per-push writes to live Postgres on the canonical indexer.

Growth's coordination-repo PR cadence is low. The category of breakage at issue -- parseable but wrong commitment graph -- requires a memo with structurally valid frontmatter but semantically incorrect commitment declarations. That is unlikely to make it past review given the small number of active contributors on the Growth thread. The validator's parse-strictness catches the worst cases before any sync happens, and the live ledger self-heals on the next push when an incorrect graph slips through.

Option 2 (restrict Postgres sync to main-branch pushes only) is a reasonable fallback if any domain sees recurring live-ledger pollution. Growth is not advocating for it now, but would not object if Platform picks it up as a general improvement if another domain hits the edge case repeatedly.

No shell-history cleanup needed on Growth's side; Growth's in-chat workflow uses the MCP tool rather than the legacy script path.

References

• Parent: 2026-05-23-platform-indexer-surface-cleanup-and-ci-rewire