Repository navigation
docs: state the real-host evidence where the threat model denied it - #22
Merged
Merged
Conversation
The threat model still opened by saying nothing in it had been observed on a real host, and decision 0002 still listed the runner under RestrictNamespaces=yes as unverified. The ARM64 acceptance showed both. - say the boundary was observed on one ARM64 host, and is unverified elsewhere - mark decision 0002's open item as verified, pointing at the evidence
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Why
docs/threat-model.mdstill opened with "Nothing in this document has yet been observed on a real host running this code". The ARM64 acceptance observed the boundary, both bycheckand from inside real jobs. Decision 0002 still listed the runner underRestrictNamespaces=yesas "not yet verified".verification.md, assumption 1, records it as holding.The earlier close-out PR (#21) fixed a similar sentence further down the threat model, and missed this one.
What changed
How it was verified
docs/acceptance/2026-10-arm64.mdanddocs/verification.md.gatecheck.Evidence level
Documentation only.
Limitations
None.
Risks
None.
Compatibility impact
None.
Remaining work
None.