I2795 — The trunk's recorded run reaches the tracked evidence ledger, and the baseline is tightened to it
Land the executions the newest green trunk run recorded (validate run 38844702397, artifact evidence, origin ci, 606 executions) in .ai/repo/evidence/ledger.json, as the recording pull request ADR 0080 proposes would, and tighten .ai/repo/evidence-baseline.txt to what that ledger supports with scripts/evidence-check --baseline.
DONE wave 0 · p1 · implementation profile · parallel safe
Objective
Land the executions the newest green trunk run recorded (validate run 38844702397, artifact evidence, origin ci, 606 executions) in .ai/repo/evidence/ledger.json, as the recording pull request ADR 0080 proposes would, and tighten .ai/repo/evidence-baseline.txt to what that ledger supports with scripts/evidence-check --baseline.
Why
On 2026-10-17 the tracked ledger held 14 local executions, so evidence show read 214 claims not run and evidence-check supported none of the guarantees, while every green trunk run records the whole suite and the crate tests in its evidence artifact and the recording pull request is not wired.
Current state
14 executions in the tracked ledger; evidence show: not run 214, stale 21, no test 12.
Desired state
The tracked ledger carries the trunk run's 606 executions; evidence show: inputs unchanged 106, stale 129, no test 12, none not run; evidence-check: 106 guarantees supported and pinned by the baseline, none lost.
Scope
- .ai/repo/evidence/ledger.json
- .ai/repo/evidence-baseline.txt
- .ai/repo/project/issues/I2795.yaml
Out of scope
- Wiring the recording pull request (ADR 0080): it needs the owner's choice of token
- Accepting ADR 0068, 0080 or 0087; acceptance is the owner's act
- Editing a row by hand: the ledger is the one the run's collector wrote
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- The ledger is the evidence artifact's ledger.json byte for byte
- scripts/evidence-check reports no guarantee lost and the baseline pins the supported ones
Validation
- scripts/evidence-check
- bin/majordomus-cli evidence show --check
Evidence required
- evidence_check_clean
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| evidence_check_clean | ci | validate run 39438896504 at master 9a5a9b77520: structure job 118683336232 runs gate evidence-check (scripts/evidence-check) (99667818df0) | success (the run's only red job is pages, which runs no test) | a81b1e3 |
Timeline
- started
- 2026-10-20T16:16:49Z
- verified
- —
- completed
- 2026-10-20T16:31:17Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2795.yaml. Read it back with majordomus plan show I2795.