docs: align architecture and proof-scope docs with kickoff decisions - #13
Merged
Merged
Conversation
The 2026-07-22 kickoff decisions (recorded in CLAUDE.md via #12) left the published design docs stale in four places: - State the day-one Rust-first binding snapshot: all capability contracts start native-Rust, the verity-consensus-sys export set starts empty, and the zone/sequence diagrams show the target state, not day one. - Mark the crate layout as the target shape; implementation starts as a single verity-consensus crate with zone boundaries as module boundaries. - Record proposer selection as settled (chain-side pure function) instead of undecided, and update the boundary-migration table accordingly. - Fix the proof-only proposition wording: the model-checking toolchain is phased in per MODEL_CHECK.md, not wired in from day one, so those propositions do not yet constrain the running Rust.
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
1 participant
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.
Why
The 2026-07-22 kickoff decisions (#12) settled the Rust-first strategy, the single-crate scaffold, and proposer-selection placement — but the published design docs still described the target state as if it were day one. This PR closes the four factual gaps found in the design review.
Changes
ARCHITECTURE.md+ docs mirror): at kickoff every capability contract is bound native-Rust, theverity-consensus-sysexport set is empty, and the diagrams show the target state.verity-consensuscrate; zone boundaries begin as module boundaries under the same inward invariant.formal-verification.md): the model-checking toolchain is phased in perMODEL_CHECK.md, not wired in from day one — until a harness targets a proposition, it constrains the design, not the running Rust.mdbook buildpasses locally.