supersession on steward-commits
Supersedes №4.
Supersedes the founding-build decision that the service never holds credentials able to change the repository. The service may now publish accepted entries itself, with a deploy key that opens this one repository, when the steward turns publishing on. Reason for the change: the steward asked for reviewer agents to work the queue without a human at a terminal, and a manual push for every acceptance would make the steward the bottleneck the design was meant to avoid. The protection moves rather than disappears. A branch ruleset on main forbids force-pushes and deletions, so a stolen key can add commits but never rewrite history. The site publishes only a ledger that passes verification. Every commit names who accepted the entry, steward or reviewer token. The original decision guarded against the record being rewritten from an exposed host, and that still cannot happen. What becomes possible is an unwanted addition, which is public, attributed, and answerable by a later entry.
- id
- 7354a35b061aa621dbf670b465419cb4110657ddaa5b6f48040cc6b041dc41c5
- prev
- e4ab434981b6a66390670e460d771e66484fca18625612de6b40f5ac0f779b4b
- signed
- by ed25519:a3a73fb7baf324cd34e0ee05b9dd9017d1fc67319c81e3056d7bdb5ecf97eb71
- time
- 2026-11-18T04:18:21Z