Fleet simulator · seed 1 · 24 files · 586 ledgered events
Run the whole trial
before you run it.
A synthetic fleet driven through the same guarded transition table the platform publishes — no shortcut edges, no agent closing a file, every authority edge charged to a human. The run is deterministic: the seed and the three exception rates fully describe it, and they live in the URL, so a result can be handed to a reviewer who will reproduce it exactly.
Median cycle
3.1 d
P90 cycle
3.5 d
Median time-to-dispatch
1.5 h
Fleet span
4.3 d
Autonomous share
61%
Human touches / file
8.5
Refusals ledgered
24
Gate coverage
26/27
PASS
Chain head 35568576a68e87d4 · every link derived from its predecessor, so a single altered event invalidates the tail.
Run configuration
Cycle-time distribution
Where the fleet actually lands.
Trial 1 measures, recomputed
What this run proves.
Guarded transitions exercised
26 of 27
Not reached: CLOSED_ARCHIVED→REOPENED
Illegal transition attempts refused
24 refused
Each file records one AI closure attempt, refused and ledgered.
Audit chain intact
head 35568576a68e87d4
586 events chained; every link derived from its predecessor.
Human touches per file instrumented
8.5
Authority edges cannot be executed by an agent.
Time-to-dispatch measured
1.5 h median
Median from intake to first valid dispatch attempt.
Every file reaches closure
24 of 24
Closure is human-authored after final guards re-run.
Guard coverage · 26 of 27 documented transitions
Every edge, and how many times the fleet crossed it.
RECEIVED → VALIDATING
×24Assignment created; validation workflow starts.
VALIDATING → PENDING_INFORMATION
×6Required field or evidence missing / conflicted.
PENDING_INFORMATION → VALIDATING
×6New required information received.
VALIDATING → COMPLIANCE_REVIEW
×24Identity, duplicate and lender configuration gates pass.
COMPLIANCE_REVIEW → DISPATCH_READY
×24Readiness checklist passes; no blocking hold.
DISPATCH_READY → DISPATCHED
×24Vendor eligible at point of dispatch; approval valid.
DISPATCHED → AWAITING_VENDOR_RESPONSE
×29Dispatch delivery initiated successfully.
AWAITING_VENDOR_RESPONSE → VENDOR_ASSIGNED
×24Vendor accepts while the attempt is valid.
VENDOR_ASSIGNED → ACTIVE_RECOVERY
×24Qualifying First Action recorded.
ACTIVE_RECOVERY → VEHICLE_LOCATED
×24Qualifying vehicle-location event reported.
VEHICLE_LOCATED → RECOVERY_REPORTED
×24Vendor submits recovery package.
RECOVERY_REPORTED → RECOVERY_VERIFIED
×24Evidence passes identity and verification gates.
RECOVERY_VERIFIED → POST_RECOVERY
×24Post-recovery workflow initializes.
POST_RECOVERY → CUSTODY_VERIFICATION
×24Custody verification starts.
CUSTODY_VERIFICATION → AWAITING_LENDER_DIRECTION
×24Custodian known; critical issues resolved.
AWAITING_LENDER_DIRECTION → TRANSPORT / DISPOSITION
×24Authorized direction, no conflicting hold.
TRANSPORT → DISPOSITION
×24Authorized transport completed; handoff verified.
DISPOSITION → OPERATIONALLY_COMPLETE
×24Outcome and evidence complete.
OPERATIONALLY_COMPLETE → FINANCIAL_REVIEW
×24Financial close workflow starts.
FINANCIAL_REVIEW → FINANCIALLY_COMPLETE
×24Ledger reconciled; controls satisfied.
FINANCIALLY_COMPLETE → PENDING_FINAL_CERTIFICATION
×24Operational and financial prerequisites met.
PENDING_FINAL_CERTIFICATION → CERTIFICATION_HOLD
×6Certification deficiency discovered.
CERTIFICATION_HOLD → PENDING_FINAL_CERTIFICATION
×6Deficiency remediated or exception documented.
PENDING_FINAL_CERTIFICATION → FINAL_CERTIFICATION_COMPLETE
×24Certifications and human review pass.
FINAL_CERTIFICATION_COMPLETE → CLOSURE_REVIEW
×24Closure requested; human review required.
CLOSURE_REVIEW → CLOSED_ARCHIVED
×24Human closes after final guards re-run.
CLOSED_ARCHIVED → REOPENED
—Authorized reopen with reason and target workflow.
Fleet ledger
Open a file to read its chain.
The same registers behind this run are searchable in the evidence index, and the prerequisites that gate a real Trial 1 are scheduled on the critical path.