S

@satsuma/experiments

PublicThe system

Governed runs of Satsuma trading on tangerine over ISMP. Results are published as articles when a run completes.

Lab runs, not the live system. Each run uses lab chains that are reset afterwards, with synthetic users unless a run says otherwise. Nothing here happened on the Satsuma chain.
RunsLab run · 10 November 2026, 15:42 UTC

Rollback on trading health

When an upgrade quietly stops a product serving the trading that relies on it, is it rolled back, and is an upgrade that changes nothing for them left alone?

7/7 passed23 min

Setup

Chains
Satsuma lab chain
  • RoleHome
  • KeptLab, not retained
tangerine lab chain
  • RoleProving
  • KeptLab, not retained
Users
  • UsersSynthetic
Model
No model: scripted answers
  • ModeScripted
Operator seat
  • SeatBy delegate
Unattended
Yes: nobody was watching to step in
Time
23 min · ended 16:05 UTC

Checklist 7 items

Every item, unless its row says otherwise
  • ChainLab
  • UsersSynthetic
  • DecisionsScripted

Rolling back a bad change

6/6 passed
Pass6 items passedShow them
PassAn upgrade that made things worse is rolled back to the version before it1 of 1 attempts
PassThe rollback is triggered by the trading account's own records, not by an alarm on the contract1 of 1 attempts
PassThe rolled-back change is recorded as an incident1 of 1 attempts
PassTrading is healthy again after the rollback1 of 1 attempts
PassAfter the upgrade, the watch period ends with nothing wrong found1 of 1 attempts
PassThe watch period judges the trading after the upgrade and finds it healthy, so nothing is rolled back1 of 1 attempts

Fixing by an in-place upgrade

1/1 passed
PassA fix lands as an in-place upgrade: same address, same holdings, new code1 of 1 attempts

What this proves

  • Whether, in this run, the bad upgrade was rolled back from the trading records and the sound one was kept.

What it does not

  • The model's own judgment: model answers are scripted.

What broke, what was fixed

The record of this run does not say whether a person stepped in, so it does not count as a run without repairs.

Cost in tokens

Not recorded: this run has no chain-derived scorecard.

Archived evidence

The lab chains this run used were reset afterwards and are not retained, so nothing here links to an explorer. The record below is the archived copy.

Scorecard
None archived.