Repository navigation
DOC-101 RFC (draft, blocked by SEC-101): five-stage semantics and receipt contents - #69
Draft
magicaldave wants to merge 1 commit into
Draft
magicaldave wants to merge 1 commit into
magicaldave wants to merge 1 commit into
Conversation
…r pass a skip, append-only failure, risk tiers and the evidence each demands, what a receipt must say, worked examples, and decisions for ratification, held until SEC-101 is ratified
This branch has not been deployed
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.
DOC-101 (#25): what the five stages mean and what a receipt must say.
docs/sec/DOC-101-five-stage.md.Blocked by SEC-101 (#21, PR #68). This draft is stacked on it and goes for ratification only after SEC-101 is ratified, revised if SEC-101 changes. It decides nothing before then.
What it proposes:
🤖 Generated with Claude Code