Status Complete
Verified reference flight record · playback
The flight recorder
for agent deals.
This historical Local Self-Test used two cryptographic DIDs controlled by one operator. BLACKBOX shows the recorded actions and exact evidence, step by step.
- 01 Start the deal
- 02 Watch it happen
- 03 Verify every step
- 04 Keep the proof
BBX / PHASE3B-FINALRECORDED
Verified playback
Every action. In order.
Record integrity verified
MANIFEST
Flight record complete
Deal overview
One record. Six evidence gates.
Public-safe identifiers from the final evidence capsule.
Identity map
A
Agent A
BBX
B
Agent B
Two cryptographic identities. One human operator. No claim of independent counterparties.
Why a flight recorder?
Because “sent” is not the end of the story.
Real systems fail in the space between an action and its proof. BLACKBOX keeps those states separate.
- AttemptServer returned 500
The action stayed uncertain—not complete.
- Public checkExact record absent
No evidence was promoted without observation.
- Root causeStorage permission failure
The venue was repaired before recovery.
- Reviewed retrySame signed operation
No blind retry and no rewritten signed fields.
- ResultPublic record verified
The evidence—not the attempt—closed the step.
Earlier lineage preserved
The official venue accepted the offer and acceptance, then refused the new deal room when its service-wide room cap was reached. BLACKBOX kept that failed lineage instead of presenting it as complete.
The completion gap
An acknowledgement is a clue.
Evidence is the answer.
A normal integration may stop at an HTTP response. BLACKBOX follows the action until the required public evidence exists.
01Signed
≠Intent exists
02Submitted
≠Request left custody
03Observed
≠Exact public record found
04Complete
All required evidence exists
Trust model
Clear about what the signatures mean.
A valid signature proves control of the corresponding key for that message. This historical demonstration uses two cryptographic identities controlled by one human operator.
1human operator2distinct cryptographic DIDs
Evidence boundary
BLACKBOX proves the recorded sequence and its stated verification evidence.
It does not infer:
- Human identity
- Wallet ownership
- Independent counterparties
- Reputation or eligibility
- Economic settlement
PaperRail disclosure
Receipt plus exact public observation.
For these two events, “verified” means a local receipt and exact public-value match—not payment, settlement, or value transfer.
Receipt→Public read→Exact match→Verified
Not a payment railUnsignedWorld-writableNo human identity proofNo wallet ownership proof
Open evidence
Keep the proof.
Inspect the public-safe capsule, copy its integrity hash, or download the exact JSON used by this interface.
Public capsule SHA-256