README diagram: annotate built vs planned - #100
Merged
Conversation
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
2 participants
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.
Follow-up to #97. The trust-domain diagram now distinguishes status:
solid borders are built and gated; dashed borders are designed in
NOTES.md with no code yet — the entire release-integrity story (#3),
app-publisher sigchains and witnessing (#52), the dedicated sandbox
origin (open decision; frames today are opaque-origin srcdoc), and the
notification broker + Web Push wake path. A legend paragraph under the
diagram states this, and names the partial cases on the solid side
(grant machinery as fragments, one data service).
Render-verified against mermaid@11 under the demo's pinned Playwright
Chromium (stroke-dasharray classDefs parse and paint).
Automerge armed per org convention.