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
- Population/frame/invitation/funnel records (or an explicit declaration that open entry replaces them)
- Membership as a statused lifecycle; roster history reconstructible
- Authorised agenda items with proposer/approver/provenance
- Evidence register with disclosures
- Decision records preserving question/method/electorate/result/dissent
- Recommendation/response/acceptance/implementation as separate objects
- Supportable non-digital participation
- Dual attribution: actor + authority on every consequential action
- Published methodology for any random selection
Model-dependent
- Rotation/cohorts/staggered terms (permanent and recurring models only)
- Mixed elected+citizen membership (hybrid only)
- Self-agenda-setting machinery (Ostbelgien-class only)
- Public agenda input channels (Newham/Paris-class)
- Open participation without selection (open assemblies only)
- Multi-level nesting/delegation events (nested structures only)
- Party/organisational frames (internal sortition only)
- Mass-input channel with bias label (Pattern G only)
Governance/political choices — not software choices
| Choice | Evidence it is contested |
|---|---|
| Strata and their rationale | CA UK vs Brussels poles (SRC-0038 vs SRC-0032) |
| Attitudinal stratification | unresolved legitimacy contest |
| Agenda authority model | five distinct corpus models; no convergence |
| Response/implementation obligation | statutory → none spectrum |
| Transparency vs protected deliberation | Brussels legislates protection; theory contested |
| Delegation vs fresh sortition at higher levels | theory, untested |
| Selection algorithm | leximin vs quota-fill — a published-governance choice, not an implementation detail |
| Permanent council powers | agenda rights vs oversight role |
| Mass input’s share of agenda authority | no corpus answer |
Boundary findings
- Shared Cicada foundation candidates: people/organisations, roles, authority declarations, provenance/audit, geography, documents/evidence, permissions — all flagged with caveats in
BOUNDARY-MAP.md(assembly authority semantics exceed generic permissions). - Assemblies-specific: the entire selection chain (population rule → frame → invitation → pool → specification → run → reserves/replacement), cohort/term/rotation, remit objects, recommendations with support levels, dissent, response obligations, implementation tracking.
- External/integration candidates for CA-R3: stratified selection engines (Panelot/OpenDLP/SF library — licence verification owed), mass-input platforms (Polis/Decidim/CONSUL), async deliberation (Loomio), accountability component (Decidim Results — semantics unverified), capture/synthesis (Dembrane).
Under-served by available software (per CA-R1 landscape)
- End-to-end member lifecycle (no reviewed system)
- Receiving-authority response obligations as first-class objects (Decidim Results is nearest, manually maintained)
- Implementation tracking bound to recommendations
- Selection audit ceremonies as a reusable feature
- Offline participation inside the selected-assembly lifecycle
- The connective layer itself — practitioner labour today fills it
Before CA-R3 (technology/reuse assessment)
Must be resolved:
- Licence verification for Panelot and Dembrane Echo (carried from CA-R1).
- Whether Decidim accountability semantics match the response-obligation model here (CA-REQ-061–064).
- Whether OpenDLP’s seed/witness model satisfies CA-REQ-013–015.
- 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
- Which strata are legitimate for which populations
- Whether attitudinal criteria are permissible
- How much agenda authority selected members hold
- Whether recommendations bind anyone and how strongly
- Delegation fractions in nested systems
- Whether permanent sortition institutions should exist at all in the target polity
- Who audits the auditors — the governance level above the witness model
What CA-R2 deliberately did not do
- No platform selection; no reuse decision; no architecture; no schemas; no APIs; no sortition engine; no real participant data; no InfoScope integration. Those remain CA-R3/CA-A1/CA-AI1 scope and gated.
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
- All
requirements/records;research/methods/METHOD-COMPARISON.md;research/theory/THEORY-TO-PRACTICE.md;research/software/CAPABILITY-LANDSCAPE.md; corpus case files - SRC-0017, SRC-0021, SRC-0027, SRC-0030, SRC-0038, SRC-0043, SRC-0047, SRC-0078, SRC-0084, SRC-0100, SRC-0109, SRC-0111, SRC-0118, SRC-0120, SRC-0125