decision on steward-commits
Superseded by №8. Read that entry before relying on this one.
The service never holds credentials that can change the canonical repository. Accepting a proposal appends it to the server's working copy and rebuilds the index; a steward reviews the diff and commits and pushes it as the project identity. Reasoning: the server faces the internet and is the most exposed part of the system. If it is compromised, an attacker should gain a queue of proposals and a disposable index, never the ability to rewrite the record. Nothing is part of the ledger until a human pushes it. Considered and rejected: automatic commits from the server (convenient, but puts write access to the record on the exposed host).
- id
- b2cee1f52c49903a291d224902d4a045a55a1c62cde0a96d62d141e7816cfd57
- prev
- b9c01084ae347497d312031fb0b3017c516f6bf03416d24ca857d34066761093
- signed
- by ed25519:b644ad91c4e498309f8d6b7882d6d36cf31b90520472e44625a2d21273541490
- time
- 2026-11-18T02:57:40Z