Decision packet
Hold for human review.
- Evidence receipts
- Remaining gaps
- Owners + deadlines
- Reflex replay
01 · U.S. state expansion
Every new state creates a new proof burden.
Rules change. Licenses renew. Audits ask for receipts. The evidence is scattered.
OperatingCalifornia
ExpandingTexasCan we prove we are ready?
Start with the business problem: expansion creates more evidence work before it creates revenue. Our fictional demo company is moving from California to Texas.
02 · The patchwork
Compliance teams search. ProbaFide assembles proof.
- 01Requirements
- 02Licenses
- 03Renewals
- 04Audit receipts
State expansion is a patchwork problem. The product does not decide the law; it organizes the evidence a human needs to make that decision.
03 · ProbaFide
Upload the files. See what they prove.
Four plain review steps. Exact receipts. Clear human actions.
Local evidencePDF · DOCX
CSV · MarkdownNames + sizes + SHA-256
CSV · MarkdownNames + sizes + SHA-256
Internal tests
Decision packetIdentify
Assess
Respond
ReportPreliminary · human review
Assess
Respond
ReportPreliminary · human review
The user chooses local documents. ProbaFide organizes the review into four plain steps, with evidence locations and a next owner for every gap.
04 · Product runtime
AI reviews. Code validates. Humans decide.
- 01Reflex isolationFresh workspace · restricted network · replay
- 02One evidence agentChooses inspection + tools inside the evidence and approved-source boundary
- 03Deterministic validatorHashes · schema · evidence tests · scores
- 04Human decisionPreliminary report · accountable owner
One scan uses one evidence agent—not a hidden swarm.
Be precise here. Reflex isolates execution and preserves the replay. One evidence agent autonomously chooses inspection and tool steps inside the evidence and approved-source boundary. Deterministic code validates the contract. A human owns the decision.
05 · Runtime auditability
Sanitized live activity—not private reasoning.
- #01 · FileEvidence acceptedSHA-256 receipt recorded
- #05 · CommandNormalize evidenceExit 0 · stable locators created
- #12 · SourceApproved source checkedNetwork policy recorded
- Final · ValidationReport contract passedRequired results · scores recomputed
No prompts. No secrets. No command arguments. No document bodies.
The screen exposes safe operational facts: accepted files, approved commands, sources, and validation. It never claims to expose the model's private reasoning.
06 · Hackathon build
One Codex window. Four specialist tracks.
OrchestratorOne Codex window
- FrontendUpload + live activity
- BackendLaunch + polling + replay
- EvidenceFour steps + strict schemas
- PresentationWebsite story + speaker flow
ProofTests → deploy → browser checks
Build-time specialists. Product runtime: one evidence agent per scan.
During the hackathon, one Codex window delegated four build tracks in parallel. That is how we built the product, not how customer scans run.
07 · Fictional Texas demo
A decision packet—not another dashboard.
Evidence28% → 90%coverage
Open checks19 → 4unresolved
Risk100 → 60highest unresolved
Evidence you can inspect. Decisions humans must own.
The remediated demo improves evidence coverage and reduces open checks, but it still does not authorize launch. That is the value: clearer evidence and a safer human decision.