Repository navigation
registry: MC-002, MC-003 and MC-004 owner re-review 2026-11-02, evidence unchanged - #40
Merged
Merged
Conversation
…nce unchanged
Owner attestation, 2026-11-02: "I re-reviewed MC-002, MC-003, MC-004;
evidence unchanged." No trigger fired: every pinned hash still matches and
every support URL resolves.
One MC-004 pinned file, guard_llama_guard_4_benign.jsonl, could not be
evaluated in the owner's 18:37 verify_claims.py run (fetch timeout). It
verified unchanged in the 18:10 run and again at 18:49 on this claims.yaml
("matches bound ref", exit 0).
Only last_reviewed moves, and last_owner_review with it, since it may not
lag the newest claim review. The homepage's dateModified follows
last_owner_review, as in 1d1e76a. Every page generated from claims.yaml is
regenerated; distribution is re-bound in the next commit.
…arries the MC-002..004 re-review
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.
Owner re-review of MC-002, MC-003 and MC-004, dated 2026-11-02. The three claims failed
verify_claims.pyonly on their 60-day review windows (last reviewed 2026-08-28, 08-30 and 08-31). Every pinned hash matched and every support URL resolved.Owner attestation, 2026-11-02: "I re-reviewed MC-002, MC-003, MC-004; evidence unchanged."
Commits
052aa29registry (16 files):last_reviewed→ 2026-11-02 on the three claims;last_owner_review→ 2026-11-02, since it may not lag the newest claim review;dateModified, as in 1d1e76a;claims.yaml, regenerated.ca575afdistribution (6 files): drafts and events re-bound to the registry commit.draft-history.jsongains 4 revisions, as in registry: GV-001 states the hosted build in its scope, re-pinned to ghost-visualizer 2ce5a96 #38. Every event binding iscommitted.e0fac0esitemap: lastmod follows the commits above.No commitment field changes, so
claims_history.yamltakes no transition.Verification on this branch
python3 scripts/verification_manifest.py:ok deterministic verification manifest: 90 unique checks, exit 0.guard_llama_guard_4_benign.jsonlcould not be evaluated in one 18:37 run (fetch timeout). It verified unchanged at 18:10, at 18:49 and in the manifest run above ("matches bound ref").What this does not change
scripts/publication_gate.pystill requires five unfamiliar-reader records;publication/readers.jsonhas none.Order
This merges first. A census transport branch stacks on it as a separate PR: 33 unexamined candidates, N/M/K unchanged at 20/14/5, with MC-001's re-pin. After that comes the cadence-rows PR. Do not merge until CI is green and the owner has reviewed.