Repository navigation
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
§13.11 rung 1 — quorum shadow verdict Shadow mode: this records a verdict and merges nothing. A refusal |
… (Refs #6450) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Oct 27, 2026
Member
Author
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.
Lands docs/specifications/PVB-001-proof-code-bridge.md, byte-identical to the arbiter-cop handoff file (sha256 prefix f127e2d95108, verified after copy). Relayed order AC-1130-pvb. Docs only: one spec file, PMAT-6450 fragment, regenerated roadmap.yaml. No BR row is started here; per the order none starts until 0.72.1 ships, then BR-0 first.
Rule 10 (public-safe) scan, by me, against the spec's own rule text. I do not hold the operator's private-term list (it is operator-side), so this is a pattern scan, not that list: no hosts, absolute paths, repo tiers, budget figures, token figures or revenue appear. It does contain generic mentions that private operator-side artifacts exist ("operator's infra repo", "operator-side" PVL ledger/spec, a private budget sidecar, and the repo-relative name scripts/pvl/lib.sh at line 16). I left the text unedited to keep it byte-identical; the non-author reviewer should judge whether those lines are acceptable and the operator-side list scan still has to run.
Size: 676 insertions, 638 of them the one spec file; I found no size check on main that applies.
Not armed (workers never arm). Needs the cop's non-author 3/3.
Closes #6450
🤖 Generated with Claude Code