Every proof page on this site so far has said, plainly, that its examples are illustrative. This page is different. It documents one real, measured instance of the governed screening pipeline — run internally on a live inbound deck, journaled end to end, and published here in redacted, anonymized form. One run, one record, one number, with the caveats stated as plainly as the result.
The input was not a constructed sample. It was a live $2M seed deck from an energy-infrastructure software company — identity withheld pending the company's consent to publication.
The question in front of the operator was the standard screening question: should this deck advance to partner review? The deck was screened through the governed due-diligence pipeline described across this site — typed evidence, adversarial review, calibrated confidence, gated authority, and a full decision and execution record at the end. This page shows what one real pass through that pipeline looked like, and what it measured.
The governed-autonomy ladder — Evidence → Calibrated confidence → Gated authority → Full audit trail — is usually described in the abstract. In this run, each rung left a concrete, journaled mark.
9 typed claims were extracted from the deck. 3 were flagged as contradicted; 1 — the company's live prototype URL — was independently verified. 3 cross-claim conflicts were detected deterministically, before any paid model call was made.
A Red/Blue adversarial review argued the deck both ways, with integrity validation on the output (blue_role_adherent=true). Confidence was capped by what could actually be verified — a verification-capped screen, not a persuasion contest.
One cloud judge call ran under a $5 / 3-call fail-closed spend cap. The engine's authority ended at a recommendation: decision support only, with no autonomous investment action available to it.
Every claim, conflict, verdict, gate, and spend event was journaled into a decision and execution record, released digest-bound to the human operator.
The replay below walks the screening run stage by stage — claim typing, deterministic conflict detection, the adversarial review, the judge call, and the gated release.
Annotated replay of the measured screening run. Real engine output; the presentation is reconstructed for clarity and anonymized for publication.
The screen did not produce a hedge. It produced a verdict, a capped confidence, the conditions that would change the picture, and a human decision on top.
A decline is a feature here, not a failure. The system is not judged on flattering a deck; it is judged on producing a screening decision a reviewer can hold accountable — verdict, evidence, cap, conditions, and the human decision, all in one record.
During this engagement, the operator caught the adversarial-review component producing prosecution-formatted “defenses” — the defending side echoing the attacking side's format instead of doing its job. Three defective runs were refused for publication.
The platform was fixed, not the story: output validation on the adversarial roles, a governed retry, and operator-visible integrity flags — all with tests. The workflow was then re-run cleanly, and that clean validation re-run is what this page publishes.
The part that matters. The screen verdict was identical before and after the fix. The evidence cap decides the outcome — not the narrative quality of any single component.
In a live walkthrough we run a governed workflow on representative inputs and show every rung of the ladder — and the decision and execution record it leaves behind.
Browse the demo library → Read the decision and execution record →