Research / requirement

Current research

CA-R2 synthesis — comparative models and requirements

Type: requirement Updated: 2026-10-05 Scale: cross-jurisdictional Path: requirements/CA-R2-SYNTHESIS.md

requirementssynthesis

Sources: SRC-0017SRC-0021SRC-0027SRC-0030SRC-0038SRC-0043SRC-0047SRC-0078SRC-0084SRC-0100SRC-0109SRC-0111SRC-0118SRC-0120SRC-0125

CA-R2 synthesis — comparative models and requirements

CA-R2 closing synthesis. Updated: 2026-10-05. Answers the phase question: what institutional models must Cicada Assemblies be capable of representing and supporting, without prematurely choosing one constitutional model?

Answer in one paragraph

Cicada Assemblies must represent the lifecycle and the institutional variation within it: one-off, permanent-rotating, standing-local, hybrid-elected, open, party-internal and mass+mini-public patterns all exist in the accepted corpus and differ in their legitimacy source, selection basis, agenda authority, mandate and accountability machinery. The constants across all of them are the record contract (provenance, dual authority/permission attribution, immutable outputs, tracked response chain) and the selection governance separation (authorised specification vs reproducible execution). The variables are constitutional choices that software must hold as declared parameters, never as defaults.

Common to almost all models

Model-dependent

Governance/political choices — not software choices

ChoiceEvidence it is contested
Strata and their rationaleCA UK vs Brussels poles (SRC-0038 vs SRC-0032)
Attitudinal stratificationunresolved legitimacy contest
Agenda authority modelfive distinct corpus models; no convergence
Response/implementation obligationstatutory → none spectrum
Transparency vs protected deliberationBrussels legislates protection; theory contested
Delegation vs fresh sortition at higher levelstheory, untested
Selection algorithmleximin vs quota-fill — a published-governance choice, not an implementation detail
Permanent council powersagenda rights vs oversight role
Mass input’s share of agenda authorityno corpus answer

Boundary findings

Under-served by available software (per CA-R1 landscape)

Before CA-R3 (technology/reuse assessment)

Must be resolved:

  1. Licence verification for Panelot and Dembrane Echo (carried from CA-R1).
  2. Whether Decidim accountability semantics match the response-obligation model here (CA-REQ-061–064).
  3. Whether OpenDLP’s seed/witness model satisfies CA-REQ-013–015.
  4. Whether the connective layer is built, integrated or institutional-method-only — the genuinely undecided boundary question.

Before CA-A1 (architecture)

Must be resolved: 5. Which institutional patterns the first deployment must support (this phase deliberately did not choose). 6. Personal-data boundary: what Cicada holds vs operators hold (respondent pools vs frame custody). 7. Multi-level ambition in v1 (models 1–5 differ enormously in build surface).

Genuinely constitutional/political questions engineering must not decide

What CA-R2 deliberately did not do

Acceptance state of this phase

The catalogue holds 68 stable requirements (59 foundational, 8 model-dependent, 1 optional). Seven institutional patterns and five multi-level models are compared. CA-R2 is complete as a requirements phase: CA-R2 COMPARATIVE MODELS AND REQUIREMENTS COMPLETE — AWAITING OPERATOR ACCEPTANCE.

Sources