Research / requirement

Current research

Requirements — mandate types and receiving-authority response

Type: requirement Updated: 2026-10-05 Scale: cross-jurisdictional Path: requirements/MANDATE-AND-RESPONSE.md

requirementsaccountabilitymandate

Sources: SRC-0017SRC-0021SRC-0027SRC-0030SRC-0038SRC-0041SRC-0043SRC-0047SRC-0111SRC-0118

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:

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

Requirements

Open questions

Sources