Repository navigation
docs: v0.4 council reviews; public-key signing deferred - #26
Merged
Merged
Conversation
Three read-only reviews of the v0.4 design (gpt-6-astra via Codex CLI, Claude Fable 5.1, Claude Opus 5.5), verbatim, plus a synthesis of the consensus changes. The design is marked deferred: with a single maintainer and no in-cluster verifier the shared-key MAC stays the accepted boundary; resume before the webhook, a secretless Action for fork PRs, or a second maintainer.
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.
Records the council review of the v0.4 public-key signing design and marks the design deferred. Docs only.
docs/dev/council-v0.4/: the brief, the three verbatim reviews (gpt-6-astra via Codex CLI read-only; Claude Fable 5.1; Claude Opus 5.5) and a README summarizing the consensus changes to make before implementing. The main ones are a signed policy index with serial and expiry, no key discovery from the policy tree, and strictness once a trust root is configured. The README also lists the three open decisions for when this resumes.