chore(catalog): enroll the 12 judgment-instrument repos - #225
Merged
Conversation
These repos were on disk and picked up by the scanner but absent from the
catalog entirely, so they carried a blank lifecycle state and were invisible
to portfolio health, risk, and attention tooling.
Each state is set from the repo's own bytes rather than uniformly:
manual-only (live, on-demand): portfolio-tribunal, drift-court,
regret-oracle, consolidation-map, instrument-foundry
dormant + operating_path archive (answered): corpus-court,
review-judge-calibration, calibration-bench, transcript-autopsy,
spec-shift-tribunal, canon-court
manual-only (in flight): operating-memory-os
operating-memory-os is deliberately manual-only rather than active: the
combination active + maintain + infrastructure enrolls a repo in the Tier 0
cohort, whose size is a fail-closed contract pinned in the 01:30 collector
and the 02:00 truth job. The catalog gate caught this; promoting it needs
those pins moved in the same change.
All entries are automation_eligible: false. No repo is archived here; the
archive operating_path is a recommendation for operator review.
Gate: 2991 passed, 2 skipped.
…ent-cluster-20260811
The Tier 0 boundary condition still needs to be recorded here, but the exact run times of the two pinning jobs are operational detail that belongs in the private decision record rather than a public config file.
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
1 participant
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.
What
Adds catalog entries for 12 judgment-instrument repos that were on disk and picked
up by the scanner but absent from
portfolio-catalog.yamlentirely. Theytherefore carried a blank
lifecycle_stateand were invisible to portfolio health,risk scoring, and the operator attention surface.
Why the states are not uniform
A retirement audit initially framed all 12 as one "answered cluster." Reading each
repo's own README, DESIGN, LEDGER, or RECEIPT shows three distinct states:
Live, on-demand instruments (
manual-only/maintain) — each graduated arubric with operator sign-off and declares a live protocol in its own README:
portfolio-tribunal,drift-court,regret-oracle,consolidation-map,instrument-foundry.Answered (
dormant/archive) — each delivered a verdict and has an in-reporeceipt:
corpus-court(240/240 ruled),review-judge-calibration(kappa 0.78),calibration-bench(closed at generation 6),transcript-autopsy,spec-shift-tribunal,canon-court(scaffold only, one commit, no rulings everissued).
In flight —
operating-memory-os, which has a commit dated today.The Tier 0 boundary condition
operating-memory-osis deliberately recorded asmanual-only, notactive.The combination
active+operating_path: maintain+category: infrastructureenrolls a repo in the Tier 0 cohort, whose size is a fail-closed contract pinned in
two scheduled jobs. Cohort growth previously broke the nightly digest. The catalog
test gate caught the attempt. Promoting this repo requires moving those pins in the
same change.
Safety
operating_path: archiveis a recommendation for operator review, not anexecuted action. No repo is archived here and nothing is removed.
automation_eligible: false.config/portfolio-catalog.yaml.main.Verification