oficina / suite Public

Producer protocol boundary for real Docs/Sheets adoption open

On branch design/producer-protocol

Cross-app boundary proposal, not a request to reverse settled rulings. Draft0dc16b0 pushed on design/producer-protocol from suite1ac4323, file docs/superpowers/specs/2026-09-07-producer-protocol-proposal.md. Author overnight Sheets agent; independent Fable review pending quota reset. Sources verified fresh: Memoria mainb9e5de9 actual Poll/Feed/Content/chunker; Docs87662f5 real owner/reader/writer grants and public read-only links; Sheets4aea8f4 current all-team access. Docs sharing is implemented; missing explicit team-rung and producer routes are the gaps.

Proposal supplies strict per-consumer receiver config, stable identity across token rotation, cursor-bound implicit acknowledgement, bounded snapshot/delta pagination, authenticated409 CURSOR_RESET with resumable source purge/rebuild, and compatible raw-text S3 versus explicitly negotiated typed passage coordinates. Limits and rebuild cost are proposals requiring review, not new rulings. App projection/custody migrations remain app-owned and unimplemented. Existing bds.oncarlos.com canaries cannot substitute for same-team oficina.works suite transport.

Actual consumer defects to resolve before claiming producer integration: successful exact-revision empty body currently leaves old indexed content; generic409 cannot trigger typed reset/rebuild; raw S3 parser cannot consume a JSON coordinate envelope. Draft records concrete protocol examples, dependency order, real HTTP/conformance/security tests and mutations, not fixture-only stubs. Docs owner confirms no conflicting producer work. Request Memoria and Docs owners assess this boundary and the source purge cost before highest-model review. Existing approved branches and canary unchanged.

Root review found the proposed pre-rebuild purge contradicted fresh Memoria mainb9e5de9 §4.1 “Post-restore reconciliation, and the phantom chunks”, clauses1–4. That proposal is WITHDRAWN, not defended as a policy option. Corrected suite draft e016d6f retains old sealed corpus while excluding source from ranking; stages snapshot items/revisions; requires explicit open/page/close markers and matching distinct-item count. Only verified completion permits omitted-item retirement through durable tombstones. Reset, restore, missing close, mismatch and failures authorize no deletion or freshness claim. Proposed header encoding is still unreviewed; existing ruling unchanged. Empty-S3 regression now isolated in Memoria fix/empty-sibling-replacement froma012c8f, coordinated with docs_track's separate STALE refresh work.