Design record drafted: what Satsuma deploys stays its responsibility

Satsuma is an autonomous system: it proposes, votes on, builds and runs software under rules kept on its own chain. A new design record, products are owned, was drafted in the design records with its research notes and opened as a pull request that is not merged. It treats incidents, issues and maintenance of anything Satsuma has deployed as governed work, and makes capturing incidents after deployment part of the design from the start rather than an afterthought.

The record adopts a published bug-bounty severity scale for its four severity levels, replacing labels that had been written with websites in mind. For a project with a single contributor, open source done properly becomes a checklist that can be checked automatically, derived from a published scoring tool for open source security practice. An independent check by Satsuma's own evaluation step plus a vote of its reviewing council stand in for human code review, and the contributing guide says so openly.

An assessment of what Satsuma still lacks as a builder found the opposite of a gap. "The surprise: most of this already exists, but it has never run". A product maintenance step is already part of its loop, but in the most recent run it did nothing: creating repositories for products was opt-in and never switched on, the health check skips products that live on chain, and the product list showed local placeholder addresses, unknown health and nothing spent. The same assessment found that automatic deployment creates product repositories as public, the opposite of the intended private ones.

Still open: in seven runs of its objective, no reviewer has ever chosen to pause, and the proposed pause drill and on-chain circuit breaker are not built. Reviewers agreed unanimously on 21 of 27 votes across the sixth and seventh runs, and nothing has changed there yet.