Agenda and remit requirements
CA-R2 requirements record. Updated: 2026-10-05. Agenda-setting is the corpus’s most consequential and least-studied power (research/methods/agenda-setting.md, SRC-0070). The requirement is to record agenda authority faithfully — never to exercise it.
Agenda models in the corpus
| Model | Corpus example | Notes |
|---|---|---|
| Commissioner-defined | Climate Assembly UK (SRC-0038) | commissioning committees set the question |
| Elected-body-defined | Ireland (Oireachtas resolution, SRC-0021); Brussels committees (SRC-0030) | statute/parliamentary route |
| Statute-defined | Scotland Climate Assembly (SRC-0043) | the remit is in legislation |
| Citizens’ council agenda-setting | Ostbelgien (SRC-0021, SRC-0025) | the selected council sets jury agendas — strongest citizen control |
| Public petition | Paris (SRC-0027) | petitions + member proposals + council grants |
| Public vote | Newham (SRC-0048) | public topic vote chooses wave agendas |
| Member-generated | partial in several | members may propose within a remit |
| Movement/charter | Assemble/HotP (SRC-0066) | self-defined |
| Mixed | most real institutions | e.g. statute remit + member refinement |
Requirements to represent
For each agenda item / remit, record:
- who may propose — the authorised proposer classes (commissioner, parliament, council, members, public petition, public vote, movement);
- who may approve — the approving authority (may differ from proposer);
- scope constraints — the legal/policy envelope the item must stay within (statute terms, remit boundaries);
- question wording — exact text, versioned; wording is politically consequential and must carry provenance;
- amendments — who may amend, the amendment chain, approval of amendments;
- conflicts — where proposed items conflict (duplicate petitions, contradictory remits) and the resolution path;
- provenance — every agenda item traces to an authorised actor and approval event;
- reasons for inclusion/exclusion — rejected proposals must carry recorded reasons (agenda exclusion without reasons is an accountability hole).
Authority vs permission
Agenda authority is an institutional fact; software permission is a technical fact. A facilitator with edit rights does not acquire agenda authority by holding them. The record model must therefore hold two parallel truths:
- authority: who was entitled to set/approve/amend the agenda (governance record);
- action: who performed the edit/entry (technical record).
A change with valid technical permission but no valid authority is a violation the system must be able to represent and flag, even though software cannot adjudicate legitimacy (see AUTHORITY-VS-PERMISSION.md).
Requirements
- An assembly’s agenda must be expressible as one or more authorised items, each with proposer/approver/scope/wording/provenance.
- Agenda-setting power must be a declared property of the institution model (e.g. Ostbelgien council has it; CA UK does not), not implied by UI capabilities.
- Public agenda input (petitions, topic votes, open submissions) is a distinct channel with its own eligibility rules and bias label — it feeds agenda authority; it is not itself the authority unless the model says so.
- Members’ right to propose or request items must be representable where the model grants it.
Open questions
- Who arbitrates when two authorities claim agenda rights (commissioner vs council)?
- Whether member-generated items need a quota/threshold mechanism.
- How exclusion reasons are disclosed without chilling proposal.