Overview
Every count below carries the number it was taken from. A count of runs opens the list of exactly those runs; a count of incidents is out of every incident raised from the stored runs.
Runs
Stored in 1 pipeline. A pipeline here is a declared stage list: runs that declare the same stages, in the same order. No record names its pipeline.
Records agree
Verified: the check held, with the run's output files present.
Changed vs baseline
1 of 2 runs changed vs baseline
Changed: the run was the candidate in a stored comparison that found a first difference.
The baseline is the run each was compared with; this console picks none. 1 of 2 runs are no comparison's candidate.
Incidents
0 incidents raised from 0 of 2 runs. This console keeps no open or closed state for an incident, so none is called open.
What the evidence establishes · 2 runs
Each rung is a separate question, with its own evidence.
| Records agree | 2 of 2 · 0 held without their output files required · 0 couldn't check · 0 contradict · 0 not checked |
| Signed by a known recorder? | 2 yes |
| No declared stage missing | 2 of 2 · 0 missing a declared stage · 0 not established |
| Re-runnable stages re-run and matched | not checked · this console runs no re-check |
| Action authorized, effect confirmed | No records · This console does not record authorization. |
| Committed by a known time? | 2 not anchored |
Needs attention first · 1 of 2 runs
Order: contradicts itself, then couldn't check, then not checked, then a declared stage missing, then last attempt failed, then changed vs baseline; newest first within each.
- Changed vs baseline · demo-run-2 ·
Recent runs · 2 of 2
| Run | Pipeline | Declared stages delivered | Vs baseline | Records | Received |
|---|---|---|---|---|---|
| demo-run-2 | P1 | 6 of 6 declared stages; 1 retry recorded | First difference · model | Verified | |
| demo-run-1 | P1 | 6 of 6 declared stages; 1 retry recorded | Not compared | Verified |
Pipelines · 1
A pipeline here is a declared stage list: runs that declare the same stages, in the same order. No record names its pipeline.
| Pipeline | Declared stages | Runs | Verified | Contradicts its record | Couldn't check | No verdict recorded | Latest received |
|---|---|---|---|---|---|---|---|
| P1 | request → context → tests → model → proposal → config applied | 2 of 2 | 2 of 2 | 0 of 2 | 0 of 2 | 0 of 2 |
Verdicts by day received
Each day's verdicts are counts of the runs received that day. A marker row between two days names a recorded settings or code digest that differs from the day before, in a pipeline with runs on both days.
| Day received | Runs | Verified | Contradicts its record | Couldn't check | No verdict recorded |
|---|---|---|---|---|---|
| 2026-10-10 | 2 | 2 of 2 | 0 of 2 | 0 of 2 | 0 of 2 |