Governed Autonomy
Solutions
Venture Capital Investment Research OS Entrepreneur CAIaaS — AI Strategy CMaaS — Marketing CPaaS — ProductBoardCouncil — Boards ↗
Platform
Architecture Security Integrations Deployment Demos Trust Center Readiness Scorecard Insights Pricing Get Started →
Meta3 ecosystem
Real internal workflow — anonymized · single measured instance · redacted for publication · decision support only, no autonomous investment action · run date 2026-07-14 · last reviewed 2026-07-14

From a seed deck to an accountable screening decision

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.

A real deck, a real screen

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.

What was on the table measured instance

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.

What the engine did, rung by rung

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.

Evidence

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.

Calibrated confidence

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.

Gated authority

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.

Full audit trail

Every claim, conflict, verdict, gate, and spend event was journaled into a decision and execution record, released digest-bound to the human operator.

Watch the run, annotated

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 governed screening workflow (anonymized)

Annotated replay of the measured screening run. Real engine output; the presentation is reconstructed for clarity and anonymized for publication.

A decline — and a human accepted it

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.

The screen verdict measured instance

  • Verdict DECLINE at the screen stage.
  • Conviction 28/100, confidence LOW — capped because company-specific independent verification was near zero at the deck-only stage.
  • Conditions 9 verification conditions were journaled: the specific things that would need to be independently verified for the picture to change.
  • Human gate The human operator reviewed the record and accepted the screen outcome. The release was digest-bound and journaled.

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.

What one instance actually measured

The measured result single instance

In this measured internal workflow instance, the system produced a first review-ready evidence and decision artifact in ~19 minutes elapsed with ~13 minutes of active operator time, against a manual baseline estimate — recorded before the run — of 2–3 hours elapsed and ~2 hours active for the same scope. Engine execution: 51–100 seconds; model spend under one cent. The initial instance's adversarial pass later failed an integrity review (see below); the published replay is the clean validation re-run of the same intake — same claims, same verdict. Operator time was AI-assisted under human gates. Single instance: not an average, not a guaranteed outcome.
Why you can trust this number

The runs we refused to publish substantiated

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.

What this page is not

Read the caveats before the number substantiated

  • Internal workflow This is our own operating workflow, run by our own operator — not a customer case study.
  • One instance A single measured run. Not an average, not a benchmark, not a guaranteed outcome.
  • Deck-only evidence The screen stage worked from the deck and independently checkable signals. The deeper verification stage has not run.
  • Anonymized The company's identity is withheld pending its consent; details that could identify it have been redacted.
  • Decision support only The output is screening support for a human decision — not investment advice, and no investment action was taken by the system.
See it run on your workflow

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 →