Pilot · Design partners
Prove one governed AI workflow in 30–60 days
Recon pilots are bounded proof engagements—not platform tours. You pick one consequential workflow, we govern it at the Policy boundary, and you leave with Trust Receipt and Ledger evidence your operators can review in Mission Control.
Pilot offer
One consequential AI workflow · One Policy boundary · One Trust Receipt trail · One Ledger record · Measurable operator outcome
Qualification
Good pilots need three things
- A consequential AI action that matters if it executes wrong
- A meaningful approval or authority boundary your team must defend
- Real need for defensible proof—not another dashboard without receipts
Not a fit if
- Exploratory AI demos without a production workflow to instrument
- Architecture evaluations with no operator owner for the pilot scope
- ROI promises before the first governed interaction ships
01 · Who this is for
Who is this pilot for?
Teams deploying AI agents, copilots, or autonomous workflows in regulated or trust-sensitive environments—where one wrong action needs attributable proof, not reconstructed chat logs.
- Legal, healthcare, financial, or security operators with a live workflow candidate
- An engineering lead who can send the first governed interaction within Week 1
- A compliance, risk, or ops reviewer who will inspect Trust Receipts in Mission Control
02 · What we will govern
What will Recon govern?
One workflow. One Policy boundary. Recon observes the governed interaction, evaluates it against your Policy, and returns a permit, hold, or escalation your workflow can enforce—without collapsing evidence, authority, and execution into one opaque model decision.
- Scope: one consequential use case (e.g., intake routing, remediation hold, allocation escalation)
- Policy: one authority boundary your team already names in runbooks or approvals
- Trust Atom: each governed interaction produces a decision you can inspect and retain
03 · What proof you will receive
What proof will you receive?
Every governed interaction produces inspectable proof. The Trust Receipt captures action, Policy decision, and authority context. The Ledger appends durable evidence tied to the same correlationId—so reviewers do not depend on stitched logs.
- Trust Receipt — open the artifact and see why Recon permitted, held, or escalated
- Ledger — confirm the entry persists for retention and audit export
- Mission Control — operators review holds and escalations without learning internal runtime vocabulary
Recon requires approval before this action proceeds.
- correlationId
- tacorr_8f3a2b1c4d5e6f708192a3b4c5d6e7f8
- receiptId
- a1b2c3d4e5f6789012345678901234567890abcdef1234567890abcdef123456
- decision
- require_approval
- policyId
- policy_pilot_authority_boundary
- actionType
- pilot_scoped_governed_action
Ledger
The Ledger is your durable evidence spine—every Trust Receipt links back to the same correlationId for retention and audit.
- correlationId
- tacorr_8f3a2b1c4d5e6f708192a3b4c5d6e7f8
- ledger.entryId
- b2c3d4e5f6789012345678901234567890abcdef1234567890abcdef1234567890
04 · What the pilot measures
What does the pilot measure?
Success is operational and evidence-based—not a marketing ROI slide. We measure whether your team can govern one workflow, retain proof, and hand outcomes to an operator reviewer within the pilot window.
- First Trust Atom shipped with API key and governed-interaction docs
- Policy boundary enforced on live or staging traffic for the scoped workflow
- Trust Receipt volume and Ledger audit pass with your reviewer
- Mission Control review completed for at least one hold or escalation
05 · What happens next
What happens next?
Apply with your workflow candidate and operator owner. We confirm scope fit, align on the Policy boundary, and schedule a Week 1 kickoff. Self-serve evaluators can parallel-path with an API key—pilots add bounded founder support for the proof plan below.
- Application review for workflow fit and authority-boundary clarity
- Kickoff: API key, integration path, and Policy draft for the scoped use case
- Weekly checkpoints against the 30–60 day proof plan milestones
- Close-out: evidence pack from Trust Receipts + Ledger—not unsupported ROI claims
Proof plan
30–60 day proof plan
Week-by-week milestones from first API key through Ledger audit and Mission Control review. Outcomes are pilot-scoped—no production ROI guarantees.
Week 1
API key + first Trust Atom
Issue API key, send first governed interaction, open sample Trust Receipt.
Weeks 2–4
Policy + receipt volume
Bind Policy to the scoped workflow; accumulate Trust Receipts on live or staging traffic.
Weeks 5–6
Ledger audit
Reviewer confirms Ledger entries, correlationIds, and retention export for the pilot scope.
Weeks 7–8
Mission Control review
Operator walkthrough of holds, escalations, and close-out evidence—not a platform capability menu.
Success criteria
- One scoped workflow governed end-to-end
- One Policy boundary enforced with inspectable decisions
- Trust Receipt + Ledger evidence retained for reviewer export
- Mission Control review completed for operator handoff
Pilot outcomes are scoped to your chosen workflow—illustrative sample evidence only; no measured customer ROI or production guarantees on this page.
Apply
Apply for pilot
Share your workflow candidate, authority boundary, and operator reviewer. We evaluate pilot fit—not a product wishlist.