Propose inactive Pack execution fences and receipt journal
Delayed Pack workers can write after their execution or claim changes. This pair adds dormant protocol-2 fences, exact replay/context CAS, and independently committed bounded provider observations before active phase writes.
Successor checks are green; renewed root source acceptance is pending. The prior API0f5f/Database186 acceptance was withdrawn after post-ready findings. Root owns all merges; do not reuse that old acceptance.
Current paired heads:
- API https://github.com/recoupable/api/pull/1286 —
ebd885f0aa895746713722e712fe58264aa0c034 - Database https://github.com/recoupable/database/pull/141 —
c9d87b85ca53339f4084f8e62ed7c7ac5115f491
Post-ready repairs check action/context/attempt/replay before expiry, prevent precharged submission IDs and premature completion, fence bound dispatch uncertainty, replay expired settlement exactly, and restrict receipt append isolation. API foundation writes retain observed and own-acknowledged versions across the complete batch, rejecting competing changes in both new and saved-foundation paths. Receipt response validation and qualification oracles are stricter. SQL remains an inactive proposal outside migration/deployment runners.
Validation:35 actual disposable PostgreSQL tests including11 legacy controls;424 scoped API tests;6 separately run actual API/SQL cases including concurrent foundation CAS; required Pack/production types and lint; actual compiled SDK failure/replay checks with25 source bindings and0runtime network attempts. Current GitHub Actions pass, including full API tests, workflow fixtures and durable-port compilation. Database automated successor review found0newissues. API successor review found one nonblocking hypothetical multi-asset fixture extension, explicitly deferred against the current single-asset contract. All42 inline threads have evidence-backed dispositions; advisory suggestions are not claimed implemented.
Independent Catalog Database successor review passed. The independent Context foundation successor re-review and renewed whole-pair root acceptance remain separate gates. Original red evidence is preserved; green checks do not replace those decisions.
No hosted SQL, migration publication/apply, provider/config/renderer activation, paid live execution or App2269 closure is authorized or claimed. Public REST/MCP and legacy execution remain protocol1 without a new stale-worker guarantee.