Skip to content

registry: MC-002, MC-003 and MC-004 owner re-review 2026-11-02, evidence unchanged - #40

Merged
Cubits11 merged 3 commits into
mainfrom
claude/mc-002-004-review-2026-11-02
Nov 3, 2026
Merged

Cubits11 merged 3 commits into
mainfrom
claude/mc-002-004-review-2026-11-02

Conversation

@Cubits11

@Cubits11 Cubits11 commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Owner re-review of MC-002, MC-003 and MC-004, dated 2026-11-02. The three claims failed verify_claims.py only 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

  • 052aa29 registry (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;
    • the homepage dateModified, as in 1d1e76a;
    • every page generated from claims.yaml, regenerated.
  • ca575af distribution (6 files): drafts and events re-bound to the registry commit. draft-history.json gains 4 revisions, as in registry: GV-001 states the hosted build in its scope, re-pinned to ghost-visualizer 2ce5a96 #38. Every event binding is committed.
  • e0fac0e sitemap: lastmod follows the commits above.

No commitment field changes, so claims_history.yaml takes no transition.

Verification on this branch

  • python3 scripts/verification_manifest.py: ok deterministic verification manifest: 90 unique checks, exit 0.
  • Each of the 90 checks also run individually without stopping at the first failure: 90 exit 0, none exit 2.
  • MC-004's guard_llama_guard_4_benign.jsonl could 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

  • Deployment stays blocked. scripts/publication_gate.py still requires five unfamiliar-reader records; publication/readers.json has none.
  • MC-001 is untouched here. It is due 2026-11-13.

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.

…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.
@Cubits11
Cubits11 merged commit 8787695 into main Nov 3, 2026
6 checks passed
@Cubits11
Cubits11 deleted the claude/mc-002-004-review-2026-11-02 branch November 3, 2026 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant