Skip to content

DOC-101 RFC (draft, blocked by SEC-101): five-stage semantics and receipt contents - #69

Draft
magicaldave wants to merge 1 commit into
vnext/sec-101-threat-modelfrom
vnext/doc-101-five-stage
Draft

magicaldave wants to merge 1 commit into
vnext/sec-101-threat-modelfrom
vnext/doc-101-five-stage

Conversation

@magicaldave

Copy link
Copy Markdown
Member

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:

  • per-stage entry and exit criteria;
  • statuses, where a skip is never a pass;
  • append-only failure and retry rules;
  • four risk tiers and the evidence each demands;
  • the contents every receipt must carry (DOC-102 owns the format);
  • three worked examples;
  • five decisions for ratification. One of them reconciles the issue's "Human PR merge remains required" with the standing authority the approver granted.

🤖 Generated with Claude Code

…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

No deployments
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