Cicada gap analysis
CA-R3 record. Updated: 2026-10-05. Gaps remaining after credible reuse/integration — explicitly guarding against the fallacy “no single platform does everything, therefore Cicada should build everything.”
Anti-fallacy statement
Absence of an end-to-end platform is evidence of modularity, not of a mandate to build one. Most CA-R2 surfaces are well-served. What follows is only what remains unserved or under-served once reuse/integration is assumed.
Genuine software gaps (nobody credible supplies these)
| Gap | CA-REQs | Why it is a gap |
|---|---|---|
| Authorised selection-specification artefact | 010–012, 016, 021 | targets exist in OpenDLP; governance-authorised, versioned, legal-basis-carrying spec objects do not |
| Witness/reproducibility bundle | 013–015 | seed capture, witness attestation, re-run package — Decidim’s die-roll is the nearest convention, undocumented in selection tools |
| Dissent/minority-report objects | 053 | Loomio records votes not minority statements; everywhere else absent |
| Response-obligation objects | 061–065 | recommendation/response/acceptance/implementation as separate tracked objects — Decidim accountability is nearest and manually maintained |
| Exclusion-event records | 072 | “selected but could not participate” is recorded nowhere |
| AI-artefact boundary | 084 | no system structurally labels AI syntheses vs authoritative records |
| Multi-level/nesting relations | 090–092 | absent corpus-wide |
| Member status lifecycle | 025–030 | group membership ≠ roster-history-reconstructible assembly membership |
Interoperability gaps (things exist but don’t join)
- Respondent pool → selection run → roster handover: seams are CSV/manual between OpenDLP and anything downstream.
- Decision record → response object: deliberation tools end at “result”; response chains live outside.
- Provenance across systems: no shared event/provenance vocabulary — every integration asserts rather than evidences.
- Retention rules for respondent/pool data (CA-REQ-019): not a feature of any candidate.
Shared Cicada foundation needs (become clearer)
- Dual-attribution event model (actor + institutional authority) — CA-REQ-080.
- Authority artefacts as first-class records — CA-REQ-081.
- Permission/authority separation in audit — CA-REQ-083.
- Signed/pinned record export for reproducibility — CA-REQ-002/014 adjacency.
Assemblies-specific lifecycle needs (unavoidable)
- Eligible-population rule + frame-coverage records (003/004).
- Selection-specification governance artefact (010/011).
- Witness ceremony packaging (013/014) — thin, mostly method.
- Cohort/term/rotation records (026).
- Remit objects with proposer/approver/exclusion reasons (035–037).
- Recommendation immutability + support levels + dissent (052/055).
- Receiving-authority response chain (061–065).
Institutional/process requirements (never software)
- Choosing strata, quotas, weights; attitudinal-criteria permission.
- Agenda authority; evidence balance; facilitation judgement.
- Response obligations; support provision; member protection.
Unresolved evidence
- Panelot source/licence —
unresolveduntil SF publishes or clarifies. - OpenDLP seed/witness model — undocumented at retrieval.
- Dembrane Echo API surface + privacy model — unverified.
- Decidim accountability-component semantic match to CA-REQ-061–064 — needs component-level reading at CA-A1 if Composition B pursued.