Mandate and receiving-authority requirements
CA-R2 requirements record. Updated: 2026-10-05. Response obligation is the corpus’s strongest institutional differentiator (METHOD-COMPARISON.md reading 1). This record separates what an assembly is empowered to produce (mandate) from what the receiving institution owes in return (response obligation) — and from what actually happens (implementation).
Mandate types
Ordered by institutional weight — not a ranking to adopt, a vocabulary to represent:
- Consultation — output solicits views; no institutional commitment implied.
- Advisory recommendation — the corpus’s dominant type; recommendation issued, response courtesy or committed.
- Agenda-setting — the body may place items on an institution’s agenda (Ostbelgien council sets jury agendas, SRC-0021; Newham public topic vote feeds council agenda, SRC-0048).
- Scrutiny / oversight — standing review role (Your Party’s sortition oversight function is internal analogue, SRC-0059–SRC-0062).
- Formal response required — the authority must respond (type below).
- Justified rejection required — authority may reject only with published reasons (Ostbelgien, SRC-0021).
- Delegated decision — the body’s output binds within a declared scope.
- Veto — the body may block but not make.
- Legislative / constitutional authority — output carries direct legal force. No corpus case implements this — representable as a type, evidenced nowhere.
The critical separation
recommendation — what the assembly produced (assembly's object)
response — what the receiving authority said (authority's object)
acceptance — the authority's stated position inside the response
implementation — what was actually done (observed over time)
These are four separate institutional states. Collapsing them is the corpus’s main accountability failure mode: a response is not acceptance, acceptance is not implementation, and implementation claims must be evidenced independently (SRC-0027, SRC-0043).
Receiving-authority concepts
- Recipient institution — the body formally designated to receive the output; may be absent (Assemble has none).
- Response deadline — declared period (Scotland: statutory 6 months, SRC-0043).
- Response status —
accepted/partially accepted/rejected/modified/deferred/no response; plusoverdueas a derivable state when a deadline lapses. - Reason / justification — required where rejection or modification occurs; required by the mandate type where the mandate is justified-rejection.
- Implementation commitments — specific undertakings inside a response, each individually trackable (one response → many commitments).
- Modified acceptance — where the authority claims acceptance with changes; the modification must be shown against the original recommendation text (which is immutable — see
DECISION-AND-DISSENT.md).
Requirements
- Mandate is a declared property of the institution/cycle, recorded before the assembly runs — not inferred from outputs.
- The recommendation object and the response object are distinct, separately authored, separately versioned, separately attributable.
- No response must be representable as a state — silence is a legitimate (and common) outcome to record, not a null to hide.
- Deadline compliance must be computable from recorded dates (due date vs response date).
- Multiple recipients and multiple responses per recommendation must be representable.
Open questions
- Semantics of partial acceptance (per-recommendation vs whole-output).
- Who formally declares “modified” vs “accepted” where the authority’s self-report is the only source — independent verification is a gap.
- Whether delegated-decision mandates are ever legitimate for sortition bodies — corpus theory cautions against silent delegation (SRC-0111).