Research / analysis

Current research

CA-R3 synthesis — technology and reuse assessment

Type: analysis Updated: 2026-10-05 Scale: cross-jurisdictional Path: technology/CA-R3-SYNTHESIS.md

technologysynthesis

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

CA-R3 synthesis — technology and reuse assessment

CA-R3 closing synthesis. Updated: 2026-10-05. Recommendations are advisory (reuse/adapt/integrate/reference/omit/unresolved) — no implementation authority is claimed; architecture belongs to CA-A1 + operator decision.

Mature capabilities Cicada should probably not rebuild

Credible reuse candidates

Better as integrate

reference only

unresolved

The actual missing layer

Not platforms — the governed record spine: eligibility rules, authorised selection specs, witness bundles, statused membership, authorised remits, decision records with dissent, response objects, implementation commitments, exclusion events, AI-artefact labels, nesting relations. Every one is thin engineering but thick institutional meaning. This is the connective layer the CA-R1 landscape found filled by practitioner labour — CA-R3 confirms no assessed product now supplies it.

CA-R2 requirements still poorly served

013–015 (witness/reproducibility packaging), 019 (retention rules), 025–030 (statused membership), 035–037 (authorised-agenda objects), 053 (dissent objects), 061–065 (response/implementation chain), 072 (exclusion events), 080–084 (authority-artefact + AI-boundary), 090–092 (nesting). See REQUIREMENT-COVERAGE.md.

Shared Cicada foundation clarity gained

Assemblies-specific capabilities that remain unavoidable

Questions CA-A1 must resolve

  1. Composition posture: records-with-channels (D) vs coordinator (A/B) — the framing decision.
  2. Engine consumption: wrap sortition-algorithms (adapt) vs consume OpenDLP (integrate) — GPL boundary either way.
  3. Canonical store shape for the record spine (still no schema decisions).
  4. Which public-input platform, if any, v1 needs.
  5. Offline member-lifecycle mechanics — unserved everywhere; design or method?
  6. Personal-data custody boundary between Cicada and operators.

Is a Cicada-native selection engine justified?

No. The published engine satisfies the fairness/optimisation requirements. Cicada’s unavoidable selection-side work is the specification artefact + ceremony/audit packaging + lifecycle joins — thin layers around an existing engine, not an engine.

Smallest plausible Cicada Assemblies technical responsibility

The governed record spine + ceremony layer: eligibility/frame/spec records, witnessed run packaging (consuming an existing engine), statused membership/roster history, authorised remit/evidence/decision records with dissent, the response→implementation chain, and labelled seams to optional external participation tools. Everything else is integration or method.

Completion state

All nine named systems assessed with pinned evidence; licences resolved or marked unresolved; 68 CA-REQs mapped; composition options compared without choosing. CA-R3 TECHNOLOGY / REUSE ASSESSMENT COMPLETE — AWAITING OPERATOR ACCEPTANCE.

Sources