What is red
Three standards checks are red on main at 5f82b635, and on every open PR, from one root cause:
Registry Verify / Registry + topology in sync
Self Test / Repo self-tests, through two scripts:
scripts/tests/build-registry-test.sh: "--check on a clean checkout" fails.
scripts/tests/build-scorecards-test.sh: three claimed passes run bash scripts/build-registry.sh --check, which now exits 1. They are component-readiness-grades/M3, estate-constitution/M2 and neurosym-a2ml/M5.
None of the three is a required context, so PRs still merge. But no standards PR can be fully green while this lasts. The self-test step "Lock-gate pin is not stale" runs after the failing test step, so it is skipped on every PR. The guard is therefore not running at all right now.
Cause
#1072 (51eeca7e) and #1075 (5f82b635), merged 2026-09-30, changed files under rhodium-standard-repositories/ without regenerating the registry. Regenerating changes exactly one line:
home = "rhodium-standard-repositories/"
-source_hash = "sha256:bc9c99e1d48f9b6ca6985fc705976ed0fee560d60c1d3259e1647a382b76a1e1"
+source_hash = "sha256:51b38eb327df7ea430078bd75566d15ab9a6618f19a3b9ee7c2a1cfb8ce6adda"
Why this is not fixed in a drive-by PR
The drifted artefact is .machine_readable/REGISTRY.a2ml. The owner has ruled A2ML dead as a format. So choosing between regenerating it in place and moving the registry off .a2ml is the owner's decision, not an agent's.
Acceptance criteria
🤖 Generated with Claude Code
https://claude.ai/code/session_01QYY8Gp4v4x2J7iSNn1vZ57
What is red
Three standards checks are red on
mainat5f82b635, and on every open PR, from one root cause:Registry Verify / Registry + topology in syncSelf Test / Repo self-tests, through two scripts:scripts/tests/build-registry-test.sh: "--check on a clean checkout" fails.scripts/tests/build-scorecards-test.sh: three claimed passes runbash scripts/build-registry.sh --check, which now exits 1. They arecomponent-readiness-grades/M3,estate-constitution/M2andneurosym-a2ml/M5.None of the three is a required context, so PRs still merge. But no standards PR can be fully green while this lasts. The self-test step "Lock-gate pin is not stale" runs after the failing test step, so it is skipped on every PR. The guard is therefore not running at all right now.
Cause
#1072 (
51eeca7e) and #1075 (5f82b635), merged 2026-09-30, changed files underrhodium-standard-repositories/without regenerating the registry. Regenerating changes exactly one line:Why this is not fixed in a drive-by PR
The drifted artefact is
.machine_readable/REGISTRY.a2ml. The owner has ruled A2ML dead as a format. So choosing between regenerating it in place and moving the registry off.a2mlis the owner's decision, not an agent's.Acceptance criteria
bash scripts/build-registry.sh --checkexits 0 onmain.Registry + topology in syncandRepo self-testsare green onmain.🤖 Generated with Claude Code
https://claude.ai/code/session_01QYY8Gp4v4x2J7iSNn1vZ57