Boundary map — shared foundation vs Assemblies-specific
CA-R2 requirements record. Updated: 2026-10-05. Classifies each requirement area by where it belongs. This is a requirements boundary map, not architecture — classification here informs CA-R3 (technology/reuse) and CA-A1 (architecture); it does not perform them. Nothing is assumed already implemented.
Classifications
- shared Cicada foundation candidate — likely common across Cicada products
- Assemblies-specific — belongs to the assemblies lifecycle
- external/integration candidate — plausibly delegated to existing software at CA-R3
- institutional method only — requirement is a governance procedure, not a software capability
- unresolved — boundary genuinely undecided
Likely shared-foundation candidates
| Concept | Why shared | Caveat |
|---|---|---|
| People / organisations | common to every Cicada surface | assemblies need population rules, not just person records |
| Roles & relationships | generic org/role structure | assembly roles carry institutional-authority semantics beyond permissions |
| Authority declarations | Cicada-wide need for provenance of decisions | assemblies add authorised specifications as artefacts |
| Provenance / audit trails | shared principle | assemblies demand witness/reproducibility grade for selection events |
| Geography / jurisdiction | shared location model | assemblies need frame coverage metadata, not just places |
| Documents / evidence | shared record handling | assemblies add evidence-governance (balance, disclosure) semantics |
| Permissions | shared access control | must remain separable from authority (AUTHORITY-VS-PERMISSION.md) |
Likely Assemblies-specific concepts
- eligible population definition (rule artefact)
- invitation campaign (frame, method, weighting, funnel)
- respondent pool
- selection specification (strata, quotas, weights, legal basis)
- strata definitions and their governance provenance
- selection run (specification + seed/witness + output + audit artefacts)
- reserve / replacement lifecycle
- assembly / cohort / term / rotation
- remit and agenda-authority objects
- recommendations with support levels
- dissent / minority statements
- response obligation and response objects
- implementation tracking / commitment objects
- mass-input channel with declared bias profile
External / integration candidates (for CA-R3, not decided)
| Capability | Corpus evidence | CA-R3 question |
|---|---|---|
| Stratified selection engines | Panelot, sortition-algorithms, OpenDLP (SRC-0073–SRC-0080) | reuse vs wrap vs reimplement; licence verification |
| Mass public input | Polis, Decidim, CONSUL (SRC-0082–SRC-0094) | channel as integration vs native |
| Async deliberation/decision | Loomio (SRC-0089, SRC-0090) | fit to member lifecycle |
| Accountability tracking | Decidim accountability component (SRC-0084) | semantic match to response-obligation model |
| Conversation capture/synthesis | Dembrane Echo (SRC-0098) | facilitation-support niche |
Institutional-method-only
- choosing strata and their political rationale
- agenda-setting authority itself
- evidence-balance judgements
- facilitation judgements in the room
- the response obligation (an institutional commitment)
- deciding which institutional pattern a polity adopts
These requirements are satisfied by recorded governance process; software records them, it does not perform them.
Unresolved boundaries
- Whether the invitation funnel and respondent pool are Assemblies-specific or a shared “engagement funnel” concept.
- Whether mass-input channels belong to Assemblies or a broader Cicada participation surface.
- Whether implementation tracking generalises into a shared commitment-tracking concept for other Cicada products.