CA-A1 synthesis — architecture and contracts
CA-A1 closing synthesis. Updated: 2026-10-05. Answers the phase question: what exact canonical objects, relationships, authority boundaries, lifecycle contracts and external seams must Cicada Assemblies define?
The architecture in one sentence
Cicada Assemblies is a governed record spine — a canonical store of institutional objects and witnessed events — to which external participation, deliberation and selection capabilities attach as removable seams, and against which all authority is dual-attributed (actor + artefact).
What was defined
- 33 canonical objects (
CA-OBJ-001–033) covering institution/cycle/session separation, population/frame/invitation, selection spec/run/bundle, membership transitions, remit/agenda, evidence, deliberation records, decision/dissent, response/implementation chain, nesting, authority artefacts, external channels, provisions and exclusion events. - 7 conceptual contracts (
CA-CONTRACT-SEL-001,PART-001,DELIB-001,INPUT-001,CAPTURE-001,ID-001,OFF-001) — vendor-neutral seams; no adapters coded. - A shared Cicada foundation boundary (
CICADA-FOUNDATION-BOUNDARY.md) — what Assemblies expects from foundation contracts, without asserting CORE state. - An InfoScope boundary (
INFOSCOPE-BOUNDARY.md) — AI advisory surfaces permitted, authoritative paths structurally closed; does not activate CA-AI1. - Explicit state machines (
STATE-MACHINES.md) — assembly, spec, membership, recommendation and response lifecycles with invalid-transition rules. - Fail-closed deny paths (
FAILURE-PATHS.md) — 23 failure modes with refuse-or-flag-visible behaviour. - Synthetic examples (
SYNTHETIC-EXAMPLES.md) — five institutional patterns exercised end-to-end on fixture data. - Contract versioning (
CONTRACT-VERSIONING.md) — versioning, negotiation, deprecation and immutable historical interpretation. - An architecture decision register (
ARCHITECTURE-DECISIONS.md) — 15 stableCA-ADdecisions. - Three-layer selection architecture: authorised specification → deterministic engine → witness bundle; engineered for an external engine first.
- Dual attribution everywhere: permission ≠ authority; consequential events record both; divergences are flaggable records.
- Immutability where it matters: closed recommendations, decision records, audit bundles, historical agenda versions.
- Offline parity by construction: every member-facing interaction has a declared non-digital route; offline acts produce identical canonical events.
- Privacy classes with asymmetric retention: non-selected respondents get the tightest class; selection engine sees only anonymised projections.
Institutional-model support check
All seven CA-R2 patterns are representable without constitutional hard-coding:
- One-off advisory (A) — institution + single cycle, courtesy/statutory response models both available.
- Permanent rotating (B) — term/rotation model on institution; staggered memberships; self-agenda authority declarable.
- Standing local recurring (C) — recurring cycles + public-input channel links.
- Hybrid elected+sortition (D) — mixed membership model declared on the institution.
- Open/self-selected (E) — frame type
open+ no selection run; legitimacy basis declared not implied. - Party-internal (F) — organisational-roll frame type; population rule is the instrument.
- Mass input + mini-public (G) — INPUT-001 channel with bias label feeding evidence/agenda.
Open questions deferred to implementation/operator
- Storage implementation (append-only semantics — ledger vs event-sourced vs audited-relational is an implementation decision).
- Exact privacy-data custody split for deployments that do need imported respondent rows.
- Seam priorities for v1 (which external tools, if any, first).
- Physical/digital hybrid ceremony mechanics for witness bundles.
- Whether authority artefacts need a formal policy language or remain descriptive.
- Cross-component verification of actual CORE capability against the shared-foundation boundary (conceptual boundary defined; implementation not assumed).
- CA-AI1 InfoScope ingestion mechanics — boundary declared here; contract separately gated.
What CA-A1 deliberately did not do
No code, schemas-as-code, migrations, APIs, adapters, deployments, vendor commitments or constitutional-model selection. CA-AI1 and runtime implementation remain gated.
Completion state
24 architecture records + index. CA-A1 ASSEMBLIES ARCHITECTURE AND CONTRACTS COMPLETE — AWAITING OPERATOR ACCEPTANCE.