Satsuma
S

@satsuma/experiments

PublicThe system
Clone

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.

Readiness

Not yet

Ready when a full unattended run passes with no repair.

No published run has passed every item unattended without a repair yet.

Runs since the last repair
0
Capabilities proven
24of 24
Time per run · median 1 h 23 min
1 h 34 min
  • Council governance, proven
  • Defending against market manipulation, proven
  • Fixing by a migration, proven
  • Fixing by a setting change, proven
  • Fixing by an in-place upgrade, proven
  • Fixing by redeploying, proven
  • Handling a cross-chain outage, proven
  • Handling liquidity withdrawals, proven
  • Lineage to the objective, proven
  • Operating a product within its limits, proven
  • Product direction from measured use, proven
  • Products that depend on each other, proven
  • Recovering from its own failures, proven
  • Refusing changes that corrupt stored data, proven
  • Refusing products that break their own rules, proven
  • Replayable test runs, proven
  • Retiring a product cleanly, proven
  • Reviewing its own products, proven
  • Rolling back a bad change, proven
  • Stolen-key safety, proven
  • Stopping and restarting a product, proven
  • Tracking security advisories, proven
  • Trading calmly in an ordinary market, proven
  • Trying and judging improvements, proven
Merge checks1/1 passedlast 6 November

Runs

Newest first · 23 runs

  1. 11 November · 1 h 34 min

    Pass

    Products that depend on each other

    When one product depends on another, is the dependency declared, are breaking changes refused, and is the dependent told what changed?

    • ChainLab
    • UsersSynthetic
    • ModelLive and replayed
    15/15 passed

    1 h 34 minrepairs not recorded

  2. 11 November · 4 h 35 min

    Inconclusive

    Product improvements

    Can an improvement be proposed, approved, built, measured to a verdict on chain and removed when it does not help, with no outside help?

    • ChainLab
    • UsersSynthetic
    • ModelLive and replayed
    35/38 passed

    4 h 35 minrepairs not recorded

  3. 10 November · 22 min

    Pass

    Product direction

    Does the system decide from measured use which products to keep, freeze or leave alone, and does its planning session put its choices to the council?

    • ChainLab
    • UsersSynthetic
    • ModelLive and replayed
    10/10 passed

    22 minrepairs not recorded

  4. 10 November · 5 min

    Pass

    Lineage to the objective

    Does every product, build and piece of work trace back to the root objective, and is work with no objective refused?

    • ChainLab
    • UsersSynthetic
    • ModelScripted
    5/5 passed

    5 minrepairs not recorded

  5. 10 November · 1 h 37 min

    Inconclusive

    The test bench

    Can a run be started from a saved chain state and its model calls answered from a recording, so that the same result comes back without calling the model again?

    • ChainLab
    • UsersSynthetic
    • ModelReplayed
    1/5 passed

    1 h 37 minrepairs not recorded

  6. 10 November · 23 min

    Pass

    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?

    • ChainLab
    • UsersSynthetic
    • ModelScripted
    7/7 passed

    23 minrepairs not recorded

Earlier runs

10 November

9 November

8 November

6 November

5 November

4 November

2 November

29 October

Each page is the record of one run as the harness wrote it: the question it was set up to answer, a verdict for every item on its checklist, the evidence it left on the lab chains and what it cost in tokens. There is no write-up; conclusions wait until the system is complete.