Research / architecture

Current research

CA-A1 — canonical ownership boundaries

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/OWNERSHIP-BOUNDARIES.md

architectureownershipboundary

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

Canonical ownership boundaries

CA-A1 architecture record. Updated: 2026-10-05. Defines what Cicada Assemblies owns canonically vs what external systems may supply.

Canonical Cicada Assemblies records (system of record)

ObjectCanonical ownerNotes
Assembly institutionCicadathe legal/institutional identity
Institutional model/configurationCicadadeclared pattern + parameters (CA-R2 patterns A–G)
Eligible-population ruleCicadaversioned artefact
Invitation/frame recordCicadaframe type + coverage + weighting declaration
Selection specificationCicadathe authorised governance artefact (CA-REQ-010/011)
Selection run recordCicadaspec ref + input digest + output + metadata
Witness/audit bundleCicadaseed capture, witnesses, digests, verification instructions
Respondent-pool referenceCicada (data may be operator-held)pool descriptor + digest, not the data itself by default
Membership/cohort/term stateCicadastatused roster history
Reserve/replacement eventsCicadaevent records, not just a pool
Agenda/remitCicadaauthorised items with provenance
Evidence-register referencesCicadaregister + rationale; blobs may live elsewhere
Session/deliberation metadataCicadastructure + attendance + facilitation model; content may be external
Decision/recommendation/dissentCicadathe immutable record contract
Receiving authorityCicadaidentity + obligation declaration
Response obligationCicadadeadline + state machine
ResponseCicadathe response object; receiving authority authors it
Implementation commitmentCicadacommitments + milestones + evidence refs
Follow-up/accountability recordCicadaperiodic review events
Delegation/nesting relationshipsCicadamulti-level structure
Authority artefactsCicadathe authority/permission separation layer

External / non-canonical capabilities

CapabilityCandidate systemsOwnership position
Selection algorithm executionsortition-algorithms (adapt), OpenDLP (integrate), Panelot (service)engine executes; run record is canonical in Cicada; engine output imported, never authoritative until recorded
Mass participationPolis, Decidim, CONSULchannel data is external; Cicada holds a channel record + bias label + imported summaries
Async deliberationLoomiothread/poll content external; session/decision records canonical
Synchronous deliberationinstitutional tools / Stanford ODP (unavailable)session metadata canonical; capture external
Transcription/synthesisDembrane Echo (licence-conditional)AI artefacts external-derived; labelled advisory, never authoritative
Identity providerexternal IdP/census servicesauthentication external; authority artefacts canonical
Frame data (electoral/resident registers)operator/registrar custodynever canonical in Cicada — reference/controlled import only

Import/reference policy

  1. External data enters as referenced artefacts: {external_system, external_id, digest, fetched_at} — the canonical record cites; it does not copy by default.
  2. Imports are versioned snapshots: imported content is pinned at fetch time with digest; updates create new import versions.
  3. Cache policy: external content may be cached for rendering; cache is never the source of truth.
  4. No overwrite rule: nothing external may overwrite a closed/immutable canonical record (recommendation text, selection output, response chain).
  5. Digest discipline: every external artefact cited by a canonical record carries a digest so tampering is detectable.
  6. Respondent/frame custody: population and respondent data default to operator custody; Cicada holds descriptors, counts and digests — personal data lands in Cicada only by explicit per-field decision at implementation.