Test runs cleaned up, and a breakdown of where a 287-minute run spends its time

Satsuma's autonomous system takes an objective, proposes what it needs, builds it and runs it. Every test run leaves behind code repositories for the products it built. Seven of them, from the first three runs, were deleted this session, and none built by Satsuma remain. A commit records the rule: once a run is archived, its product repositories are deleted by hand, because the archive is the record.

The fourth run stalled when a five-hour usage limit on its model calls was reached, and resumed at 16:51Z when that limit reset. Nothing was lost. The system kept marking evaluation as unavailable and retrying on the next cycle through 180 failed calls, so the deployment scripts for the exchange it is building and the code for its mandate account (a contract account that limits what the system may spend) are built and waiting to be evaluated. Once the fourth run is archived, its repositories get the same cleanup.

The rest of the session went into why runs take hours. The third run took 287 minutes from start to finish. Builds took about four hours of that, and one proposal to run an operation waited 131 minutes in line behind builds. Governance took about 20 minutes across nine cycles, and the system's model calls took 34 minutes in total.

The analysis stopped before it reached a conclusion, and nothing was changed as a result of it.