An action can outlive an HTTP response or a worker. Retrying without recipient evidence can repeat the external effect.
The implementation
What I built
Completed 128 synthetic actions with 128 recipient receipts in a bounded hosted run by combining approval-bound actions, fenced workers, and receipt reconciliation.
Go
PostgreSQL
Python
JavaScript
Docker
Features
Propose and approve exact action hashes
Inspect execution state and audit events
Reconcile recipient receipts after failure
Architecture
Go API, PostgreSQL approval/action storage, and a separate Go worker.
Browser workspace for proposals, approval, saved state, and audit events.
Authenticated simulated order API with SQLite receipts and an experimental typed model-draft path.
Engineering decisions
Bind approval to the exact action hash; strict mode requires a different authorized approving actor.
Check recipient receipts before retrying an uncertain action.
Separate model draft quality from execution correctness.
Validation and measured results
13 October 2026 hosted CI verified a dated engineering baseline, including recovery, race checks, browser workflows, and restore drills.
A bounded synthetic hosted workload completed 128 actions with 128 effect receipts; it is not a production SLA or saturation result.
The frozen model evaluation stopped at 62/80 cases and already failed its declared utility and safety gates.
Limits and unfinished work
AI quality qualification remains open. Engineering checks do not qualify autonomous decisions.
The simulated recipient supplies explicit idempotency and receipt guarantees that arbitrary external APIs may lack.
No customer deployment or API cost saving is claimed.
13 October 2026 hosted run 38379352933 at commit 37517e29913e6ec66bb4cce6a4c5373785eb3370 was inspected during this review. Repository and CI links were not publicly accessible on 14 October; no downloadable receipt is attached.
