Research / requirement

Current research

Requirements — governance authority versus software permission

Type: requirement Updated: 2026-10-05 Scale: cross-jurisdictional Path: requirements/AUTHORITY-VS-PERMISSION.md

requirementsauthorityaccountability

Sources: SRC-0021SRC-0030SRC-0038SRC-0070SRC-0100SRC-0109SRC-0111

Governance authority versus software permission

CA-R2 requirements record. Updated: 2026-10-05. This is a foundational separation for the whole requirements layer.

political/institutional authority   ≠   technical access permission
(who is *entitled* to decide)          (who is *able* to act in software)

The corpus shows legitimacy-critical actions routinely performed by people with system access but contested authority (commissioners setting remits, SRC-0100; facilitators steering rooms, SRC-0106). Software must therefore record both who acted and under whose authority — and treat divergence between them as a first-class auditable condition, not an edge case.

Illustrative mappings

ActorTechnical permission they needInstitutional authority they hold
Facilitatoredit session agenda text, manage breakoutsnot the authority to define the assembly’s agenda (that belongs to the declared agenda authority, AGENDA-AND-REMIT.md)
Administrator / operatorexecute a selection runonly to run an already-authorised selection specification — no authority to choose strata, weights or members (SELECTION-REQUIREMENTS.md)
Receiving authoritypost a responsemay respond, accept, reject, modify — may not rewrite the assembly’s recommendation text (MANDATE-AND-RESPONSE.md)
Secretariatpublish records, maintain trackingmaintains records; does not own the judgements within them
System superusertechnical omnipotence for administrationzero constitutional authority — a superuser must not be able to silently alter membership, outcomes, or provenance

Requirements

Audit separation

Open questions

Sources