ORIGINAL APPROVALExample only
Invoice DEMO-1042
Atlas Supply
$10USD · approved once
Supplier payment · One underlying obligation
- Available
- $10.00
- Reserved
- $0.00
- Paid
- $0.00
Original outcomeNot started
Original authority
THE HALTSEAL WORKSPACE DEMO
Many agents.
One approval.
Hand off the work. Try another path.
See why the same payment stays protected.
One invoice. Two Agents.
A payment that refuses to become two.
A private example for each visit. No signup.
Synthetic Sandbox · No real funds.
YOUR DEMO IS READY
Come in. Try it.
A prepared company, one approved invoice and two simulated Agents.
Use your own Workspace →ONE ORIGINAL. EVERY NEXT STEP.
The work moves.
The approval stays.
Make the next move. Watch what stays attached to the original.
Your isolated example
- 1Start the payment
- 2Hand off to B
- 3Try another path
- 4Recover with evidence
YOUR NEXT MOVE
Start one approved payment.
Agent A submits the original. We deliberately withhold its reply after the fixture records the attempt.
EXPLORE THE BOUNDARY
What would you try?
Change the proposed amount, requesting Agent or payment path. This full-invoice approval stays fixed at $10.
Reload reads the stored Sandbox session. It is separate from a process crash test.
Test recovery conditions
Fixture controls simulate source evidence. A cancellation request or elapsed time alone cannot close the original.
Closing the original leaves the replacement on HOLD until fresh approval and a new check.
ONE CONTINUOUS RECORD
The evidence stays.
- Your first action starts the record.
BRING YOUR OWN WORKFLOW
Now imagine this with your Agents.
Start your company Sandbox and connect your source. Your own approvals and evidence begin there.
Each new example has its own original. Nothing here grants customer payment authority.
What this demo proves
This account uses server-stored, isolated sessions and the existing SDK synthetic HTTP fixture engine, with bounded demo request IDs. It demonstrates that engine’s reservation and recovery contract with simulated Agents. It is separate from the retained financial kernel, signed Agent custody, native provider execution and customer installation qualification. No real funds move. Session exports are illustrative records, not execution permits or independent installation proof.
Sessions expire after 15 minutes. The session cookie is limited to the demo API. We use a daily rotating hash of the network address to limit starts. Credentials are public and do not access your personal Workspace. Privacy notice · Inspect recorded implementation tests