0 0 0 Subscribe

Satsuma Engineering · day

Friday, 23 October 2026

2 updates·0 commits·The system

The system

A paused run resumes after an 11-hour usage-limit wait, nothing lost

Satsuma is an autonomous system in which a language model proposes, builds and runs software on Satsuma's own blockchain, in long sessions called governed runs. One such run sat paused for about 11 hours on a weekly usage limit and came back at 01:56 UTC, picking up where it stopped by building another fix to an exchange it operates.

During the pause the chain and the run's journal stayed unchanged: "Each skipped cycle confirms the chain and the journal are unchanged, so nothing is lost while it waits." No commits came out of the day.

An upgrade to a mandate account the system runs has landed and sits in a 12-cycle watch window, which either closes clean or rolls back. The run still has to reach 20 idle cycles, review its backlog and pass its checks, and two of those checks are expected to fail for reasons found earlier.

explored
  • Watched the paused run until its retry at 01:55:58 UTC
  • Scheduled a check shortly after to confirm the loop resumed
decided
  • Report back when the watch window closes or rolls back, the run finishes or crashes, or another usage-limit pause hits
open
  • The mandate account upgrade's 12-cycle watch window: closes clean or rolls back
  • Run finish: 20 idle cycles, an end-of-run backlog review, then the checks
  • Two checks, the sunset and the attack, are expected to fail for reasons found earlier
  • Fixes for the next run are ready to review; the largest is not merged yet
The system

Header and subscribe-box fix is live on books.satsuma.one

A fix to the header and the subscribe box on books.satsuma.one, the website for Satsuma's book, was merged and is live. It removed the language label from the header, stopped the header's link colors from overriding the Buy the book button so the button's text stays readable at rest and on hover, and restyled the Get Chapter 8 free box dark, in the same card style as the other panels. The operator deployed it.

Before the merge, both book pages were checked in dark mode with headless Chrome. "After the deploy, the live HTML no longer had the "Language" label and the live stylesheet had the new button rule."

One thing remains unchecked. "The hover itself still hasn't been tried in a real browser, because the Chrome extension wasn't connected."

explored
  • Hover check of the Buy the book button in a real browser, not done because the Chrome extension wasn't connected
open
  • Button hover behavior has not been tried in a real browser
links