Run E attempt 3 lost to a machine outage; attempt 4 started
A fourth attempt at run E, a long governed run in which Satsuma proposes, votes on and operates its own products, has been live since 01:50Z on 2026-10-22, on the same launch settings and the same code as the third. The records of attempt 3 were kept in the experiments repository, with the intervention noted.
Attempt 3 died at 04:54Z on 2026-10-21, when the Mac running it went down and every process stopped at once; the machine booted again at 06:00Z. The run was about 2.7 hours in, with two of its products open: a token exchange and a vault, and it had got through adoption. The session found nothing pointing at the run itself: "No log shows an error, and disk is fine (59 GB free), so the machine went down, not the run."
Two bookkeeping commits in the exchange's repository are carried into the new run as history. The session treats this as the designed behaviour, because the run's records are keyed to the chain.
Nothing past adoption was exercised in attempt 3, and attempt 4 has to get through adoption again before the first real milestone is reached: "Adoption alone takes about 3 hours per attempt now — three milestone votes per product, each with the 6-minute window."
- Run E attempt 3 reached about 2.7 hours in and got through adoption before the machine stopped at 04:54Z on 2026-10-21
- Attempt 4 reuses the same launch settings and code as attempt 3
- The two bookkeeping commits in the exchange's repository are carried as history in the new run, as designed, since the run's records are keyed to the chain
- Attempt 4 has to get through adoption, about 3 hours per attempt, before the first real milestone is exercised
- Nothing past adoption was exercised in attempt 3