Black-and-white view of water moving through an engineered channel
Performance Lab / Public evidence

Field Reports

The work should survive inspection: the pressure, map, operating boundary, measured result, failed gate, and next question in one public record.

  • Claims Sourced
  • Limits Visible
  • Authority Named
Proof standard

A result is more persuasive when its limits remain visible.

Field Reports separate measured facts, derived calculations, and untested hypotheses so evidence can deepen trust without becoming a performance claim.

01 / Measured Name what the run proved.

Counts, rates, receipts, and reproducible artifacts stay attached to the claim.

02 / Blocked Show what did not pass.

A failed gate narrows the authority of the system instead of disappearing from the story.

03 / Unknown Keep hypotheses labeled.

Unmeasured savings and adoption questions become the next instrumentation plan.

Report index01 records

Start with the workflow under pressure.

Each report connects an operating map to the evidence it produced and the decisions it was not allowed to make.

  1. 01 Review operationsPrepare the evidence. Keep the judgment human.49 of 50 usable evidence packets, 98 screenshots, zero external writes, and one promotion gate that held. verified#FR-2026-01May–June 2026
Bring the next field test

Measure one workflow before expanding authority.

Name the repeated handoff, decision owner, objective work, and current baseline. The first map will show whether a controlled pilot is worth running.

Owner
Workflow owner
Authority
Human decision
Proof
Baseline + map + test plan
State
ready