File the Plan
Capture the decision, owner, reversibility, timeline, and stakes.
The first public GaaS proof object
Put your AI plan on trial before reality does.
A structured, evidence-bound Trial turns a consequential plan into falsifiable Charges, demands provenance, tests both sides, and returns an operative Verdict with Tripwires.
The seven phases
One plan. Two sides. One reviewable decision.
Extract the Claims
Break the plan into Charges—observable, falsifiable claims that must be true for success.
Discovery — Demand Evidence
Collect dated, provenance-stamped evidence for each Charge. Missing evidence becomes a finding.
Prosecution
Run the Six-Month Failure Autopsy. Name the likely failure mode, missing controls, and unverified assumptions.
Defense
Present the strongest case for proceeding, with evidence and concrete controls rather than denial.
Verdict
Return one operative result: Proceed, Proceed under supervision, Revise and refile, Split into experiments, or Dismiss / defer.
Sentencing — Tripwires
Set commitments, dates, evidence-producing checkpoints, and observable conditions that can revoke the Verdict.
Decision Trial Packet
Seal the complete reasoning chain and evidence trail in the final reviewable artifact.
Verdict vocabulary
The result is operative, not decorative.
- Proceed
- Proceed under supervision
- Revise and refile
- Split into experiments
- Dismiss / defer
A Verdict without Tripwires is theater. The Packet records what must happen next, what evidence must appear, and which observation will force the decision back into review.
The Packet
The conversation is substrate. The Packet is the deliverable.
The Packet lets another reviewer see what the plan was charged with, what evidence supported each Charge, how Prosecution and Defense differed, why the Verdict followed, and which Tripwires govern the future.
Reasoning
Filing + Charges
The decision and the falsifiable claims that carry it.
Evidence
Sources + provenance
Dated records attached to the claims they strengthen or weaken.
Operation
Verdict + Tripwires
The ruling, its conditions, and the triggers for review.
Discovery pilot
The first Trial discovers the right outcome.
A pilot begins with the buyer's actual plan and desired external outcome. A bounded sample tests whether the workflow intelligence and Packet are materially useful. Buyer response is the evidence step; the method does not assume fit in advance.
Status boundary: no buyer-validation, satisfaction, or fit claim is made here.
Reframe wall
The Trial is a proof object, not a shortcut label.
- Not a premortem label
- Not a strategy worksheet
- Not a risk workshop
- Not generic subscription software
- Not a dashboard
- Not separate from GaaS
Live State Bridge
What is verified—and what remains open.
- retrieved_at
- 2026-07-30T12:46:21Z
- verification
- VERIFIED — public route, release identity, page structure, and live Trial availability. NOT VERIFIED — buyer demand, satisfaction, or commercial fit.
- stale_risk
- Dated release verification; refresh after material changes. External market evidence remains open.
- active_object
- GaaS public surface and the Decision Trial proof object.
- relevant_blockers
- Buyer contact has not established external fit; no such conclusion is presented here.
Proof before promise
Inspect the Packet structure.
The synthetic sample shows the complete artifact without presenting illustration as buyer evidence.