Run 7 starts from the latest code, then waits out a usage limit

Satsuma is an autonomous system: a language model proposes products, votes on them, builds them and runs them on its own blockchain, and the whole loop is tested in numbered runs. Run 7 started from the main line of the code, which holds every fix made so far, including one that moves the stored address of a product when it is redeployed. It runs on a Claude Code subscription with no API key, its first model call completed, and it has its own new product registry. Run 6 was archived and its repositories deleted.

Run 7 is there to see two behaviours live for the first time: whether products that depend on the exchange get an alert when the exchange (a trading contract the system built and deployed earlier) moves to a new address, and whether the operator follows a migration of a mandate that happens in the middle of an operation, within one cycle. "Neither one can be forced. Each depends on what the reviews find and on the timing."

Around 15:40 UTC the subscription reached its session limit, which resets at 17:50 UTC. "Until then, every model call in run 7 fails. The daemon keeps retrying each cycle and nothing is lost; earlier runs got through the same thing." The Claude Code session overseeing the run then reached its own usage limit and stopped, while the run kept going.

The watch set on the run ignores the limit errors but expires after 30 minutes and cannot be renewed while the session is stopped. Following run 7 to its end, archiving it and deleting its repositories are still open, and both behaviours remain untested.