Research / requirement

Current research

Requirements — shared Cicada foundation vs Assemblies-specific boundary

Type: requirement Updated: 2026-10-05 Scale: cross-jurisdictional Path: requirements/BOUNDARY-MAP.md

requirementsboundary

Sources: SRC-0073SRC-0074SRC-0078SRC-0082SRC-0084SRC-0086SRC-0089SRC-0091SRC-0094SRC-0098

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

Likely shared-foundation candidates

ConceptWhy sharedCaveat
People / organisationscommon to every Cicada surfaceassemblies need population rules, not just person records
Roles & relationshipsgeneric org/role structureassembly roles carry institutional-authority semantics beyond permissions
Authority declarationsCicada-wide need for provenance of decisionsassemblies add authorised specifications as artefacts
Provenance / audit trailsshared principleassemblies demand witness/reproducibility grade for selection events
Geography / jurisdictionshared location modelassemblies need frame coverage metadata, not just places
Documents / evidenceshared record handlingassemblies add evidence-governance (balance, disclosure) semantics
Permissionsshared access controlmust remain separable from authority (AUTHORITY-VS-PERMISSION.md)

Likely Assemblies-specific concepts

External / integration candidates (for CA-R3, not decided)

CapabilityCorpus evidenceCA-R3 question
Stratified selection enginesPanelot, sortition-algorithms, OpenDLP (SRC-0073–SRC-0080)reuse vs wrap vs reimplement; licence verification
Mass public inputPolis, Decidim, CONSUL (SRC-0082–SRC-0094)channel as integration vs native
Async deliberation/decisionLoomio (SRC-0089, SRC-0090)fit to member lifecycle
Accountability trackingDecidim accountability component (SRC-0084)semantic match to response-obligation model
Conversation capture/synthesisDembrane Echo (SRC-0098)facilitation-support niche

Institutional-method-only

These requirements are satisfied by recorded governance process; software records them, it does not perform them.

Unresolved boundaries

Sources