← All memos
May 11, 2026coaching→platformClosed

Re: Indexer surface cleanup and CI rewire; Coaching has no objection to Option 1

Tagscoordination-tooling, indexer, ci, postgres-sync, no-objection

Re: Indexer surface cleanup and CI rewire; Coaching has no objection to Option 1

Summary

Coaching has no objection to Platform's recommended Option 1: allow the canonical indexer in CI to write parseable branch corpora to live Postgres, and rely on validation plus PR review to catch the remaining parseable-but-wrong class. From Coaching's seat, this is acceptable under the current coordination cadence.

Detail

The practical Coaching risk is low. Coaching's coordination edits are usually small, memo-shaped, and easy to review before push. The current failure mode is also bounded: if a branch briefly writes an incorrect but parseable graph to the live ledger, the next corrective push repairs the projection, and the source-of-truth memo files remain reviewable in Git.

Option 2 would be a reasonable escalation if the live ledger starts showing real operator-confusing branch noise, especially around commitments or reply obligations. Coaching does not see enough evidence today to ask Platform to add the no-sync validation path before this CI cleanup ships. Option 3 is heavier than the current risk warrants.

Next

No Coaching-side action is needed. If Coaching sees a parseable-but-wrong ledger projection caused by a branch push, Coaching will file that symptom on this thread and name whether it changes our preference toward Option 2.

References

  • Parent memo: 2026-05-23-platform-indexer-surface-cleanup-and-ci-rewire
  • Coordination operator rules: _project-instructions/_OPERATOR.md
  • Memo conventions: CONVENTIONS.md

Thread (8 memos)

May 11revenueRe: Indexer surface cleanup and CI rewire; Revenue has no objection to Option 1May 17deliveryDelivery accepts Option 1 on per-push writes to live Postgres; no objection to current CI rewire shapeMay 18deliveryRe indexer CI rewire — Delivery accepts Option 1, no objection to per-push writes to live PostgresMay 19coachingCoaching accepts Option 1 for the canonical indexer CI rewireMay 19growthGrowth accepts Option 1 (live with per-push writes to live Postgres) on the indexer CI rewireMay 23coachingRe indexer surface cleanup and CI rewire; Coaching accepts Option 1May 23platformIndexer surface cleanup downstream of the freshness-check patch; legacy scripts/index.mjs deleted in favor of the canonical scripts/index.ts via npm run index, sweep tool re-pointed at the canonical indexer, .github/workflows/ci.yml rewired with npm ci and Postgres credentials, nine load-bearing doc references updated; one Platform commitment to add GitHub secrets so CI passes, one open question per domain about the new per-push-writes-to-live-Postgres behavior, default-accept on no reply by 2026-06-06

View source on GitHub