Skip to content

Schema design review: standing-approval record agenda (PR 62 lead note) + interim-default wording #64

Open

Description

@djbclark

Tracking issue for the schema design review of the standing-approval record. The agenda was recorded in #62 (docs/review-2026-11-13/14-synthesis-and-rulings.md, "Schema design review agenda", a lead note, not a ruling).

The review proposes, and the operator rules on:

  1. Whether one standing approval may cover privileged or baseline changes. Until the operator rules, a standing approval covers ordinary changes only. The check against the validator's derived ceremony class (map §9.8) stays.
  2. How persisted rejects (DC-2) apply under a standing approval. They stay.
  3. How approval_seq single use, or its high-water mark, applies to a record that authorises more than one change. It stays.
  4. Which signers a standing approval may name outside developer mode. This is ruled only for developer mode (Smaller 1).
  5. X-trust-06, which is proposed and not yet ruled.

Dropping any check other than the per-change nonce needs an operator ruling.

Wording follow-ups from the PR 62 round-6 reviews (non-blocking):

  • The interim "ordinary only" default names "a standing approval" only. Ruling L5 (B2) lists two nonce-less modes, "a hold window, or an owner-enrolled standing approval". The default should say it covers every standing mode that applies without a per-change yes (Fable round-6 nit 1, adversary round-6 info).
  • The reading's label "(lead decision, PR 62 round-3 review)" dates the wording to round 3, but rounds 4-6 changed it. It could read "(lead decision, PR 62 review)" (Fable round-6 nit 2).

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions