Research / architecture

Current research

CA-A1 — shared Cicada foundation boundary

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/CICADA-FOUNDATION-BOUNDARY.md

architectureboundaryshared-foundation

Shared Cicada foundation boundary

CA-A1 architecture record. Updated: 2026-10-05. Defines what Cicada Assemblies expects from the wider Cicada foundation — a conceptual boundary only. Maninshed/cicada-core was not inspected or modified; nothing here claims CORE already implements these contracts. Assemblies remains independently owned by this repository.

Classification vocabulary

Capability assessment

CapabilityClassificationAssemblies expectationNotes
Person/entity identityrequired shared contracta person abstraction Assemblies references without owning — CA-OBJ-011 is a shell pointing at shared identityidentity lives at foundation; Assemblies adds respondent-identity/member-identity classes (extension)
Organisationsrequired shared contractbodies referenced by ReceivingAuthority, commissioner, operatorsplain reference suffices
Geographyrequired shared contractjurisdiction/locality references on Institution + population rulesneeds frame-coverage extension — geography alone isn’t coverage
Rolesrequired shared contractrole vocabularies for actors (operator, facilitator, member, secretariat)assembly-specific roles extend a shared role base
Institutional authorityunresolved cross-component contractCA-OBJ-030 AuthorityArtefact is Assemblies-shaped; whether a shared authority-object contract exists is undecidedif CORE gains a generic authority model, Assemblies artefacts should conform — joint design needed
Technical permissionsrequired shared contractpermission checks separate from authority (dual attribution)foundation authN/authZ is expected; Assemblies adds the authority layer on top
Provenancerequired shared contractevent provenance fields (actor, authority, source, digest)Assemblies strengthens to dual-attribution + append-only (extension)
Auditrequired shared contractevent-recording capabilityappend-only semantics + ceremony bundles are Assemblies extensions
Documents/evidence referencesrequired shared contractblob/document refs with digest pinningAssemblies adds register-level governance (balance, disclosure) as extension

Boundary rules

  1. Assemblies consumes foundation contracts where they exist; it does not replicate identity/permissions/documents.
  2. Where a shared contract doesn’t yet exist (authority artefacts, ceremony bundles, dual-attribution events), Assemblies defines its own shape and flags it as a candidate for foundation adoption — an extension, not a fork.
  3. Nothing in the foundation may write canonical Assemblies records — the ownership boundary in OWNERSHIP-BOUNDARIES.md applies to sibling components too.
  4. This record does not assert anything about CORE’s current state; verification of actual CORE capability is a later cross-component task.