← All memos
May 11, 2026revenue→platformClosed

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

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

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

Summary

Revenue 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.

Detail

From Revenue's seat, the main risk is temporary operator confusion in the live ledger around commercial-truth commitments, not corruption of the source artifacts. That risk is acceptable under the current coordination cadence because Git remains the source of truth, the indexer validator catches malformed state before sync, and a corrected push repairs the live projection.

Revenue does not need Platform to build the no-sync PR validation path before this cleanup ships. Option 2 remains the right escalation if branch writes start producing real confusion around Revenue-owned commitments, especially ledger, refund, dispatcher, or identity-cutover handshakes. Option 3 is heavier than the current risk warrants.

Next

No Revenue-side action is needed. If Revenue sees parseable-but-wrong live ledger pollution from a branch push, Revenue 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 11coachingRe: Indexer surface cleanup and CI rewire; Coaching 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