Repository navigation
Add database close preparation gate - #198
Merged
Merged
Conversation
Consume live database ownership into a proof-bound ClosePending state, retain the exact adjacent clean manifest, model explicit abandonment, and add a disjoint memory clean-close checkpoint candidate.\n\nRefs #186\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>\nCopilot-Session: 9e85df59-6de2-4170-bc09-2afb36dee35f
This was referenced Aug 7, 2026
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.
Summary
LiveDatabaseinto a proof-boundClosePendingDatabasewhileretaining all database and transaction owners
manifest and construct the exact adjacent Clean Manifest V2
clean-close checkpoint candidate and deterministic fault coverage
Safety boundary
The gate preflights source-manifest identity, lifecycle, and generation before
invoking transaction candidate publication. Transaction and post-proof failures
remain terminal, retain exact ownership, expose no stale retry, and never
construct
ClosedDatabase. Clean-manifest publication remains the next focused#186 phase.
Validation
cargo fmt --all -- --checkcargo test --workspace --all-features --lockedcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo run --locked -p ntsql-architecture-checkcargo run --locked -p ntsql-contract --bin ntsql-governance -- fixturescargo run --locked -p ntsql-contract --bin ntsql-governance -- provenance-offlinecargo run --locked -p ntsql-contract --bin ntsql-governance -- provenance-onlinegit diff --checkRefs #186