Experiment 003's sixth run is the first to meet all four key results
Experiment 003 is a governed trading test, following the published Experiments 001 and 002, in which Satsuma runs a trading operation under limits it set for itself. Its sixth run finished, was archived, and is the first to meet all four key results: 10 swaps against a target of 10, 3 mandate refusals against a target of at least 1, 22 failures reconciled against a target of at least 2, and holdings in balance at the end. "The operation closed itself once it met its objective: 10 swaps, nothing pending, and holdings at 46–54% tUSD both on paper and in tangerine's live balances." Every drill passed: a relayer outage, a pool pull, a key compromise, and over-cap and low-floor requests.
Two things went wrong during the run, and both were recovered. A false halt came from mis-pinned measurement IDs; after one manual stop of the loop to fix the bug, two votes on chain re-pinned the measurements and resumed the operation. The second was a failed deployment: "The mandate's successor failed to deploy because the exchange's fix had replaced WTANG. The loop recorded the failure, kept the fix open, sent the log back to the builder, and the retry deployed." In run 4 the same kind of failure needed a hand edit.
Two fixes went through governance. An issue filed against the exchange was fixed by a redeploy and resolved in the same vote. An issue in the mandate, where the operator could block a migration, was resolved on chain through a migration vote. The migration to the new account was confirmed from balances, because this build exposes migratedTo() rather than migrated(). The results were written up, committed and pushed.
Still open: deleting run 6's two repositories waits on the operator, a further mandate issue was filed for investigation with no outcome recorded, and the balance watch expired after the run was archived and was not restarted.
- Experiment 003 run 6: every key result met; false halt recovered by votes; two fixes; migration confirmed by balancesThe system
- Monitoring run 6 through status checks across the exchange and mandate products, drills, the successor deployment and the migration
- Confirming the mandate's migration to the new account through balances
- Migration is confirmed via balance checks, because this build has migratedTo() instead of migrated()
- Deleting run 6's two repositories is waiting on the operator
- A further mandate issue was filed for investigation; its outcome is not recorded
- The balance watch expired after run 6 was archived and was not restarted