0 0 0 Subscribe

Satsuma Engineering · Monday, 19 October 2026

The system

Satsuma takes charge of both its products; exchange fix approved on retry

Run B, the run of Satsuma's ownership work now under way, executed the manifests of both products it owns: the mandate account, which trades within limits set for it, and the exchange. The mandate's manifest carried its KPI definitions over from an earlier run, run A. "This is the first time a manifest has crossed chains intact, invariants and KPIs together." The exchange's manifest was drafted from scratch.

The loop that runs Satsuma's propose-build-run cycle went through a third session-limit window, from about 17:47Z to 21:20Z. The logic that pauses the loop while the model allowance is used up held: the loop skipped cycles and made no model calls while the limit lasted. A separate build that repairs dispatch deployed to its own new repository, and a check that stops a build from deploying into another product's repository kept it off the mandate account's repository. As of the 22:29Z report, run B had no errors and no limit hits since 21:20Z.

The exchange had an open defect: in an edge case, one kind of swap reverts without giving a reason. It was routed to a fix of the router alone, so the trading pairs and their liquidity stay where they are, the same path as run A's one successful fix. The reviewer refused the first attempt because it did not cover every token a swap route can pass through, so the defect could still occur after the fix. The builder got one more attempt; it passed the reproduction check and the reviewer approved it. It is not yet deployed or merged.

Still to come: rehearsing the router change on a copy of the chain and redeploying the router, then a vote that resolves the defect and the merge of the change. A pending fix to the mandate account (the account that trades within set limits) is now eligible for its turn. Run B advances about four hours at a time between limit windows, because the logged-in subscription runs out after a few hundred model calls; switching back to the account run A used is the one change that would speed it up.

explored
  • A third session-limit window, from about 17:47Z to 21:20Z, with the new pause logic skipping cycles during it
  • A separate dispatch-repair build, deployed to its own new repository
  • A router-only fix for an edge case where one kind of swap on the exchange reverts without a reason
  • A first router fix for the exchange, refused by the reviewer as incomplete
decided
  • Route the exchange defect to a router-only fix, so the pairs and their liquidity stay where they are, the same path as run A's one successful fix
  • Give the builder one more attempt after the reviewer refused the first router fix
  • Rehearse the router change on a copy of the chain, then redeploy the router, before the vote resolves the defect and the change is merged
open
  • A pending fix to the mandate account is still waiting its turn and is now eligible
  • The router rehearsal, redeploy, vote and merge are still to come
  • Run B advances about four hours at a time between limit windows; switching back to the account run A used is the one change that would speed it up

Also on Monday, 19 October 2026