Research / analysis

Current research

CA-R3 — Cicada gap analysis

Type: analysis Updated: 2026-10-05 Scale: cross-jurisdictional Path: technology/CICADA-GAPS.md

technologygaps

Sources: SRC-0144SRC-0145SRC-0146SRC-0147SRC-0148SRC-0149SRC-0150SRC-0154SRC-0152

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)

GapCA-REQsWhy it is a gap
Authorised selection-specification artefact010–012, 016, 021targets exist in OpenDLP; governance-authorised, versioned, legal-basis-carrying spec objects do not
Witness/reproducibility bundle013–015seed capture, witness attestation, re-run package — Decidim’s die-roll is the nearest convention, undocumented in selection tools
Dissent/minority-report objects053Loomio records votes not minority statements; everywhere else absent
Response-obligation objects061–065recommendation/response/acceptance/implementation as separate tracked objects — Decidim accountability is nearest and manually maintained
Exclusion-event records072“selected but could not participate” is recorded nowhere
AI-artefact boundary084no system structurally labels AI syntheses vs authoritative records
Multi-level/nesting relations090–092absent corpus-wide
Member status lifecycle025–030group membership ≠ roster-history-reconstructible assembly membership

Interoperability gaps (things exist but don’t join)

Shared Cicada foundation needs (become clearer)

Assemblies-specific lifecycle needs (unavoidable)

Institutional/process requirements (never software)

Unresolved evidence

Sources