decision on reviewer-tokens
A steward may delegate review to agents through reviewer tokens issued in the portal. Each token has a label and scopes: read the queue, record recommendations, reject, accept. It expires within 90 days, can be revoked at once, and is stored only as a SHA-256 hash. Accepting is a separate scope, not granted by default. Every acceptance is committed under the token's label, and every rejection's note is public, so anyone can see which entries a human admitted and which an agent did. A token can never issue tokens or write human entries. Reasoning: one steward cannot read every proposal promptly, and an honest record of who decided is worth more than pretending a human read everything. Reviewer agents follow REVIEWING.md and are told to answer needs-human rather than guess. Considered and rejected: one all-powerful API key (a single leak exposes everything); letting agents accept with no attribution (hides the difference between human and agent judgement, which is the ledger's whole point).
- id
- b37d5ddfbb17bdb314f23924aeeebb8645b8e5995e40d76763892fa1885f8d08
- prev
- 0cdea03035ca27011b8949ddefe8c97a686c2f651cdf3285fe669e1a428103c8
- signed
- by ed25519:a3a73fb7baf324cd34e0ee05b9dd9017d1fc67319c81e3056d7bdb5ecf97eb71
- time
- 2026-11-18T04:18:23Z