Skip to content

feat(gateway): establish bound effects and unified recovery (AP074) - #213

Merged
bordumb merged 138 commits into
mainfrom
codex/effect-recovery-foundation
Nov 5, 2026
Merged

bordumb merged 138 commits into
mainfrom
codex/effect-recovery-foundation

Conversation

@bordumb

@bordumb bordumb commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Managed operations carry one immutable native bound effect through authorization, complete review, exact approval, admission, execution and recovery. One native journal and typed transition owner handles mutation, bounded acquisition and separate recipient disclosure. Durable grants produce single-use permits; replay, lost responses and missing ACKs cannot recreate entry, redeliver content or refund uncertain effects.

The implementation retains shared file/PostgreSQL authority, connection, configuration and epoch fences; bounded separately authorized recovery; authenticated recipient ACKs; strict private journals; public hiding projections and operator-private audit export. Installed Python/TypeScript/UI journeys consume native identities and outcomes. AP070 remains an independent application-owned reference; managed Google integration is deferred. AP073 is untouched.

Published head: 28ecb46d0ec81a2a2e402d582aea4e757d7b77ce. This coherent correction initializes pinned Lean dependencies before reuse validation in both jobs. The current-head audit requires the actual Aeneas package commit, clean checkout and reviewed warning inventory; previously a fresh checkout reached that audit before setup created the package, safely refused reuse and rebuilt. The expensive repository proof compilation remains conditional on successful validated reuse. No proof, package, current-source or fingerprint check is removed.

The native workflow guard and fresh-checkout regressions reject omitted, late, conditional or ignored dependency setup in either job. Reuse still requires a successful clean same-repository/same-PR producer with exact immutable run/job/attempt/archive provenance, complete transitive proof/generated/import/toolchain/assurance/executor inputs, and fresh current Rust/source validation. Missing or mismatched evidence runs fresh Lean.

The corrected executor changes the complete key to 9b5a7049779384207399e43d927cef5ccd856dce925ba80242c1bc0a25f929aa. The successful earlier c523 producer is not reinterpreted under that new key. This head must establish a new clean producer; a required evidence update will then verify actual warm hits in both jobs. Neither is claimed before execution.

Validation and scope:

  • Prior repaired source b54 passed all twelve applicable non-main workflows, all63 required native selectors (48ordinary/11hardening/2cost/2generated, each one pass/zero ignored), and30 additional PostgreSQL conformance cases. Source/merge tree and all eight principal artifact archives were authenticated.
  • Its authoritative implementation passed302 gateway library tests with0failures/63ignored, all six repaired fuzz corpus tests in both invocations, and semantic freeze validation. Installed Python/macOS/Linux/Windows and TypeScript, both source-free demos/owner UI, distinct-UID containment, 28request/26response mutation and22information comparisons, generated histories and cost evidence passed. Results are source-specific, not relabeled as this correction.
  • The b54 fast Lean retained log confirms the exact reuse refusal: missing formal/.lake/packages/aeneas before setup. Its safe fresh fallback passed. Older eb44 already has successful clean Lean/329statement audit, two translations,49Kani and formal aggregation for its exact old key.
  • Complete local correction verification:27 native qualification tests, workflow ownership, strict xtask Clippy, metadata generation/non-update and formal source-closure checks passed. No local Lean/Kani rerun. Exactly59existing source-citation hashes changed; all other assurance manifest bytes remained identical.
  • Freeze433 advances only assurance bytes63, source-closure bytes108, evolution86 and publicsurface433. Native protocol/SDK identities and native closure 4c368d74e5a748ac79752bf9f2da2cbb3447c9ec67755147c80c03a0856a3d81 are unchanged. Formal source closure is 09fb135d91c47ff1b2a873b583564db3467e76973c9763090bac2affd73b6837.
  • All corrected-head gates, fresh cold producer and subsequent two-job warm verification remain pending at publication. Eight named manual-main live/operator jobs are inapplicable to this PR event; skipped status supplies no live or signed-release evidence.

The acceptance audit, prior producer report and reuse contract/correction retain requirements, actual provenance and pending gates. Final validation will be recorded in this PR and authenticated local reports without a recursive documentation-only push solely to record the outcome of its own commit.

AP074 remains incomplete until final-head acceptance and required hosted gates pass. Keep this PR draft; do not merge/deploy. AP070 remains independent and AP073 untouched. Storage/durability, clocks, participating writers, recipients and OS isolation remain explicit premises. The WAL restore rehearsal reports replay_continuity=false: connection floors are not a general operation-journal rollback anchor, and point-in-time rollback of attempt/counter rows does not establish safe automatic managed resume. Live-provider qualification, provider atomicity and human attention are not claimed.

bordumb and others added 30 commits October 28, 2026 01:25
Source-SHA: cd3a344

Workflow-Run: 40621783276
Source-SHA: 8dbd993

Workflow-Run: 40628243754
Source-SHA: fd8803c

Workflow-Run: 40630469370
Source-SHA: 6d38bb1

Workflow-Run: 40631903601
Source-SHA: eb3c31f

Workflow-Run: 40636309645
Source-SHA: 3ca2c36

Workflow-Run: 40642554358
Source-SHA: 119d1f7

Workflow-Run: 40647137194
@bordumb
bordumb marked this pull request as ready for review November 5, 2026 23:55
@bordumb
bordumb merged commit 6898797 into main Nov 5, 2026
96 checks passed
@bordumb
bordumb deleted the codex/effect-recovery-foundation branch November 5, 2026 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant