Repository navigation
feat(gateway): establish bound effects and unified recovery (AP074) - #213
Merged
Merged
Conversation
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
8 tasks
Source-SHA: 977ae61 Workflow-Run: 41914022680
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 earlierc523producer 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:
formal/.lake/packages/aeneasbefore 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.4c368d74e5a748ac79752bf9f2da2cbb3447c9ec67755147c80c03a0856a3d81are unchanged. Formal source closure is09fb135d91c47ff1b2a873b583564db3467e76973c9763090bac2affd73b6837.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.