E-017 / RECORDED AUTONOMOUS EXECUTION
A dependent leg failed.
TALOS returned the unresolved capital.
One agent call entered KeeperHub. TALOS recorded the partial effect, applied the precommitted recovery route, and reconciled every reserved unit.
RECORDED EXECUTION PATH
One call.
Five verifiable effects.
Agent intent → Recovery Covenant → KeeperHub writes → declared failure → reconciled return.
-
01
AGENTOne bounded intentTalosClient.executeIntentPREFLIGHT PASSED
-
02
TALOSRecovery Covenant committedorigin-return · before dispatchKEEPERHUB LOG
-
03
KEEPERHUBForward effect recorded180.000000 mock unitsVERIFIED RECEIPT
-
04
DECLARED FIXTUREDependent leg failedinjected HTTP status 500FAILURE PRESERVED
-
05
KEEPERHUB + TALOSCommitted recovery executed119.400000 returned to originPOST-STATE VERIFIED
DECLARED FAILURE
HTTP 500 selected the rollback branch.
The organization’s HTTP Request action was Pro-gated, so the status was deliberately injected. TALOS does not call this a live Kalshi, Polymarket, or DEX failure.
COMMITTED RECOVERY
origin-return was already committed.
- Selected branch
- talos-rollback
- Function
- triggerRollbackByCommittedRoute
- Residual
- 0.000000
POLICY + LIFECYCLE + ACCOUNTING
E-017: from Covenant to recovery.
0xebc32f7e67e85db157de0811c6b7cf3eb9beb9af12c18c2682fcfd4d0526053e
RECOVERY AUTHORITY
RECOVERY COVENANT
Failure did not create a new permission.
The Saga could return only the measured Delta, through the route bound before execution.
- Covenant ID
- 0x2a9d8ad7…40d4a03
- Permitted route
- origin-return
- Asset
- script-only mock ERC-20
- Compensation ceiling
- measured STN Delta
- Covenant ↔ Saga
- MATCH
- Covenant ↔ Token
- MATCH
LIFECYCLE LEDGER
PROVENANCE- 01COVENANT COMMITTEDinitiateSagaWithCovenantLOG OUTPUT
- 02DISPATCHEDdispatchSagaLOG OUTPUT
- 03FORWARD EFFECTexecuteForwardEffectVERIFIED RECEIPT
- 04DEPENDENT LEG FAILEDinjected status 500DECLARED FIXTURE
- 05COMPENSATION SELECTEDorigin-returnCOMMITTED POLICY
- 06RECOVEREDremaining amount = 0ONCHAIN READ
ACCOUNTING PROOF
300.000000
RESERVED MOCK UNITSTHE ONE-CALL BOUNDARY
The agent did not orchestrate compensation by hand.
The Recovery Covenant and declared failure entered the same KeeperHub workflow input.
await talos.executeIntent({
covenantId: "0x2a9d…4a03",
failureStatus: 500
})
- Agent
- 0x67B87E…bcddb
- Vault
- 0xF161e0…46294
- Token
- 0x6a6097…50a3
- Revision
- 400cce2
E-017 / DETERMINISTIC RECOVERY DEMO
Run the recorded failure-to-recovery path.
Watch the exact E-017 states advance locally. This demonstration sends no transaction and creates no new Saga.
Recovery edge is committed, not generated after failure.
The demo replays the E-017 state machine without sending a transaction.
Run E-017: validate Covenant → record forward effect → detect status 500 → return 119.400000 → verify zero remaining.
E-017 / EXECUTION BACKEND
The agent called TALOS.
KeeperHub submitted four writes.
The workflow executed the bounded contract calls; TALOS retained the Covenant, Delta, and terminal accounting.
AGENT
Requests
Submits one bounded intent through the TALOS SDK.
TALOS
Constrains
Commits route, amount, asset, Saga identity, and compensation ceiling.
KEEPERHUB
Executes
Submits the assigned contract writes and exposes execution evidence.
TALOS
Reconciles
Verifies terminal onchain state and closes the accounting identity.
RECORDED JOB
- Workflow ID
- 8nbhy1mwhm2rukz2g566w
- Execution ID
- zo996sfnyab3wjwp63wuf
- Condition result
- FALSE
- Selected branch
- talos-rollback
- Write count
- 4
- Workflow enabled
- NO
EVIDENCE LIMIT
No fleet is invented here.
The current proof identifies a KeeperHub workflow and execution—not a keeper address, heartbeat, queue depth, or fleet health. Those instruments remain deferred until KeeperHub evidence supplies them.
E-017 / CAPITAL ACCOUNTING
Every reserved unit is reconciled.
The amounts below belong only to E-017 and are denominated in mock ERC-20 units.
300.000000 = 180.000000 + 0.600000 + 119.400000 HOLDSAvailable wallet balance and aggregate treasury totals are not exposed by E-017.
EXECUTION RECEIPT
E-017
0xebc32f7e67e85db157de0811c6b7cf3eb9beb9af12c18c2682fcfd4d0526053e0x2a9d8ad7e0b64ed54b68dfb4d83074ca98ef60e84e4dea7eb44c3dd4b40d4a03Transaction evidence
Proof strength remains explicit.
Failure and recovery
Injected because the HTTP Request action was Pro-gated. No live venue response is claimed.
119.400000 mock units returned. Remaining Saga amount independently verified at zero.
What this receipt does not prove
- Production USDC or mainnet custody.
- A live Kalshi, Polymarket, or DEX order response.
- Cross-venue atomicity or zero-loss reversal.
- LTN recovery or x402 settlement.