Synopsis
$ zevron.exe --versionPrint the full evidence behind a unit's verdict. This is where a trusted result stops being a claim and becomes proof.
Example
zevron — trust
zevron ❯ zevron trust store.sqlite
store.sqlite // library · persistence
funnel
T0 lint · types · contracts ✓ ruff + mypy --strict
T1 visible tests ✓ 24/24 in sandbox
T2 hidden + property tests ✓ 18 hidden · 6 properties
T3 mutation + crucible ✓ graduation gauntlet
oracle
mutation score 0.91 ≥ 0.80 gate ✓ trusted oracle
crucible — attacks survived
edge ✓ spec ✓ security ✓
guarantees
specsmith wrote tests · codewright wrote code · different models
codewright never saw the hidden suite · suite hash locked
verdict: TRUSTED attacked · held · certified
Flags
| Flag | Default | Description |
|---|---|---|
| --json | off | Emit the evidence as machine-readable output. |
| --explain | off | Include the failing case when a unit is not trusted. |
Reading the verdict
The readout has four parts:
- funnel — the tiers T0–T3 the unit cleared, with what ran at each
- oracle — the mutation score against the 0.80 gate; below it, the oracle isn't trusted
- crucible — the adversaries the surviving code held against: edge, spec, security
- guarantees — that the Specsmith and Codewright were different models, and the Codewright never saw the hidden suite
A unit is trusted only when the mutation score clears the gate and every attack is survived. When it isn't, the verdict reads not trusted and the unit returns to the forge — see the trust model for why that refusal matters.
