Repository navigation
0.7.1g1P1: mint authority for the 67 admissible appearing identities - #467
GionaGranchelli merged 2 commits into
Conversation
…ities P1 mint through the existing M30-M39 population-admission mechanism: 67 preauthorizations (16 prior adjudications + 36 G5b TOOLING_LIMITATION + 11 G5c EQUIVALENT + 4 G5d UNREACHABLE), each bound to fromBaseSha 5bcb030 (the actual squash merge of #466) and to the G6 population digest 9aebd320, with per-entry analyzer semantics and the adjudication provenance recorded in reason. The KILLED twelfth G5c identity is excluded. The population does not change; P2 consumption is out of scope. No other authority file is touched.
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Three reason fields (lines 440, 615, 640) are truncated mid-structure, dropping the UNDETERMINED second-disposition from the copied provenance, and the M36 lock makes this incomplete rationale permanent once committed.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
This PR adds data to the governance ledger config/quality/mutation-population-admissions.yml, minting exactly 67 population-admission preauthorizations ("P1") for the appearing candidate-only NON_KILLED mutation identities in :tramai-engine. It uses the repository's existing M30–M39 authority mechanism: each entry records the exact persisted row (status/outcome/family/module), the analyzer semantics it is valid under, the authority base SHA (5bcb030c…), the G6 population digest (9aebd320…), and an adjudication reason. The population itself is unchanged — P1 only proposes authorizations that a later "P2" transition consumes. The file header documentation and schemaVersion: "1" are preserved; admissions: [] becomes a 67-entry list.
I verified the mechanical invariants against the loader (MutationPopulationAdmissionLoader.kt) and the source manifests: 67 entries, all identities unique and valid 64-hex, uniform fromBaseSha/populationDigest/family/module/outcome, status split 36 TIMED_OUT · 27 SURVIVED · 4 NO_COVERAGE, category split 36 G5b · 11 G5c · 4 G5d · 16 prior-adjudication, and the KILLED identity a9760bea… correctly excluded.
Changes:
- Replace
admissions: []with 67 admission entries authorizing the appearing NON_KILLED identities, all bound to the same base SHA, population digest, and analyzer semantics. - Each entry carries an adjudication
reasoncopied from a committed G5b/G5c/G5d or P1-manifest record.
| File | Description |
|---|---|
| config/quality/mutation-population-admissions.yml | Adds 67 population-admission preauthorizations; three reason fields are truncated and drop an UNDETERMINED disposition from the copied provenance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Three of the sixteen prior-adjudication admissions carried a truncated reason field (a half-serialized Python list repr cut at 140 characters). Their complete committed chronology is now stated explicitly: final adjudication EQUIVALENT in TASK-0.7.1g1G4-RESIDUAL-11-MANIFEST.json; predecessor TASK-0.7.1g1G4-RESIDUAL-25-MANIFEST.json disposition UNDETERMINED Verified against both committed manifests: all three are UNDETERMINED in the residual-25 record and EQUIVALENT in the residual-11 record. Only the reason fields changed; identity, status, outcome, analyzer, fromBaseSha, populationDigest and cohort membership are untouched. P1 invariants re-proven: 67 admissions, 36/27/4 statuses, 36/16/11/4 provenance, 0 KILLED.
|
Correction pushed on this branch: the three truncated All three prior-adjudication admissions now carry their complete committed chronology explicitly rather than a half-serialized repr:
I verified that chronology against both committed manifests rather than copying it: all three are Only the |
689e8b6
into
epic/0.7.1-control-plane-authority

Base
5bcb030c953c425289fad9e640ab65c15936ecda— the actual squash merge of #466. Note for the record: GitHub displayedb0c79986…as the provisional merge SHA while #466 was open; that was not authoritative history and was not used. The branch is cut from the real post-merge epic tip.What this mints
Exactly 67 population-admission preauthorizations in
config/quality/mutation-population-admissions.yml, through the repository's existing M30-M39 authority mechanism. The population itself does not change: P1 proposes, P2 consumes later.a9760bea3a92):tramai-enginefor all 67fromBaseSha5bcb030c…(every entry)populationDigest9aebd3202288c82ff006f2db33c95cac0772746fa3c3061569167cd3f45df9b0(every entry)Mandatory invariants — all proven before writing
reason✓ · 8. no baseline, mutator set, timeout, family enrollment, classification semantics or ceiling change ✓ · 9. P1 performs no P2 consumption ✓ · 10. no new admissibility decision invented — every category and reason is copied from a committed adjudication ✓Reconstruction provenance
The 67 were reconstructed from committed records at the new tip, not from cached preparation: the G5b/G5c/G5d manifests and the P1 68-row manifest. The committed admissible union is exactly 67 and equals the G6 appearing NON_KILLED set (67 == 67), with the KILLED twelfth G5c identity excluded. Nothing was added, removed, rerun or substituted to make a mismatch close.
Independent verification of the written authority
Re-parsed the committed ledger independently: schemaVersion 1 · 67 entries · unique · all canonical 64-hex · exact set equality with the committed admissible union · every
fromBaseSha= the checkpoint · everypopulationDigest= the G6 digest · every entry carries a reason with its adjudication document · outcomes all NON_KILLED · statuses 36/27/4 · categories 36/16/11/4 · no KILLED identity authorized.Scope
git statusshows one changed file: the admissions ledger. Existing file header documentation preserved verbatim. No production, test, baseline, classification, enrollment, mutator, timeout or ceiling change.Explicitly out of scope
P2 is not performed. No consumption, no population transition, no baseline regeneration. G6 remains the measurement authority — the campaign was not rerun, reinterpreted or broadened.
Gates:
spotlessCheck verifyStaticAnalysis verifyChangePolicy -PchangePolicyBase=5bcb030c…BUILD SUCCESSFUL (change class runtime-behaviour, no policy violations, 1 changed file). Exact-head CI is the final authority; the admission verifiers run there. Not self-merged.