Research / requirement

Current research

Requirements — agenda and remit authority

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

requirementsagenda-setting

Sources: SRC-0021SRC-0025SRC-0027SRC-0030SRC-0038SRC-0043SRC-0048SRC-0066SRC-0068SRC-0070SRC-0100SRC-0120SRC-0131

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

ModelCorpus exampleNotes
Commissioner-definedClimate Assembly UK (SRC-0038)commissioning committees set the question
Elected-body-definedIreland (Oireachtas resolution, SRC-0021); Brussels committees (SRC-0030)statute/parliamentary route
Statute-definedScotland Climate Assembly (SRC-0043)the remit is in legislation
Citizens’ council agenda-settingOstbelgien (SRC-0021, SRC-0025)the selected council sets jury agendas — strongest citizen control
Public petitionParis (SRC-0027)petitions + member proposals + council grants
Public voteNewham (SRC-0048)public topic vote chooses wave agendas
Member-generatedpartial in severalmembers may propose within a remit
Movement/charterAssemble/HotP (SRC-0066)self-defined
Mixedmost real institutionse.g. statute remit + member refinement

Requirements to represent

For each agenda item / remit, record:

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:

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

Open questions

Sources