I3394 — The mesh lab's work-fault evidence from CI is committed as T5 trials and the T5 verdict is published with every failed trial
Convert the work-fault scenarios of a mesh-lab CI run into T5 trial records naming the run id, commit them beside I3393's, regenerate the economics projections and let the T5 row compute its status.
BLOCKED wave 4 · p1 · implementation profile · parallel safe
Blocked. This issue cannot start until I3392, I3393, I3354 are done. The status is derived from that, not declared.
Objective
Convert the work-fault scenarios of a mesh-lab CI run into T5 trial records naming the run id, commit them beside I3393's, regenerate the economics projections and let the T5 row compute its status.
Why
T5 of the owner's report of 2026-10-19; the lab's evidence lives in target/ and is gone with the runner, so the counted trials must be committed records.
Current state
target/mesh-lab/evidence.json is written per run and not tracked.
Desired state
T5 reads passed, failed or inconclusive with every trial listed.
Scope
- .ai/repo/benchmarks
- docs/generated/economics.json
- docs/generated/economics.md
- docs/generated/economics.yaml
- site/data/generated/economics.json
Out of scope
- Re-running a failed trial to replace it
Dependencies
- I3392BLOCKED The mesh lab injects the three faults into work in progress, and its evidence holds the conservation reading of each scenario
- I3393BLOCKED Each fault is injected into real coding-agent sessions on one host, and each trial's recovery and conservation reading are committed
- I3354BLOCKED A pure scorecard function computes each proof test's status, counted sample, effect and losses from committed records, and withholds a verdict until the registered sample is complete
Acceptance criteria
- Each converted record names the CI run id and scenario
- Every failed trial is listed on the T5 row
- majordomus generate --check passes
Validation
- majordomus economics proof
- majordomus generate --check
- bash test/run.sh 414_mesh_lab_evidence
Evidence required
- t5_verdict_published
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
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/I3394.yaml. Read it back with majordomus plan show I3394.