Research / architecture

Current research

CA-A1 — authority model

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/AUTHORITY-MODEL.md

architectureauthoritypermissions

Sources: SRC-0100SRC-0106SRC-0109

Authority model

CA-A1 architecture record. Updated: 2026-10-05. Institutional authority is a first-class object, separate from technical permission. “Can edit” ≠ “is authorised to approve”; “can run selection job” ≠ “may define strata”.

AuthorityArtefact (CA-OBJ-030)

Dual attribution on every consequential event

Every consequential event records two things:

Permission check: does this account have access to the operation?
Authority check:  does a valid AuthorityArtefact cover this action on this object?

Both are recorded. Neither substitutes for the other.

Divergence/exception events

An action where the actor lacked recorded authority is representable and flagged — software detects divergence; institutions adjudicate it (CA-REQ-082). A superuser’s technical ability to mutate records is itself an audit-visible event (CA-REQ-083).

Worked mappings

ActionPermission neededAuthority needed
Edit agenda draft texteditor rolenone (draft)
Approve agenda itemagenda-approver roleagenda-authority artefact
Run selection joboperator roleauthorised SelectionSpecification (locked)
Publish a responsereceiving-authority accountresponse obligation context
Amend recommendation text—none exists — immutable post-closure
Define strataspec editorspecification-authorising instrument

Rules

  1. Authority artefacts are declared objects with provenance — they exist before the actions they authorise (CA-REQ-081).
  2. Authority is scoped and dated; expired/revoked authority renders later actions flaggable.
  3. Delegation is a chain of artefacts, each link recorded.
  4. No technical privilege implies institutional authority — by construction, not by policy text.

Sources