Run 4's three gaps closed on main; run 5's test repositories removed
Satsuma is an autonomous system: a language model proposes products, votes on them, builds them and runs them, and its own blockchain records each step. Three fixes for gaps found in its fourth test run were merged into main in the satsuma repository. Fixes to a product are now opened in that product's own repository, counters carry across a migration, and a product is told when something it depends on moves.
The two test repositories from run 5, satsuma-mandate-account-r5 and satsuma-tangerine-dex-r5, were deleted. No repositories built by Satsuma are left in its code organisation. The main satsuma checkout and satsuma-exp01 are both on the merged commit.
Run 5 left work of its own: "Three gaps from run 5 are still open: 1. Confirming a migration by checking the balances when a build has no migrated() view. 2. Finding out why the rule that restarts the operator when its mandate moves didn't trigger. 3. A live test of the issue that tells a dependent product another product has moved." A later commit, Run 5's open items: migrations confirmed by balances, the operator follows a moved mandate, the relocation pass is tested, targets all three.
- Run 4's three gaps: fix PRs open, counters survive a migration, dependents learn of a relocationThe system
- Confirming a migration by checking balances when a build has no migrated() view
- Finding out why the rule that restarts the operator when its mandate moves didn't trigger
- A live test of the issue that tells a dependent product another product has moved