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
- required shared contract — Assemblies cannot function without this foundation-level contract
- Assemblies extension — concept is shared but Assemblies adds lifecycle semantics
- cannot assume current CORE implementation — concept belongs at foundation level but is not assumed built
- unresolved cross-component contract — genuinely undecided boundary, needs joint design later
Capability assessment
| Capability | Classification | Assemblies expectation | Notes |
|---|---|---|---|
| Person/entity identity | required shared contract | a person abstraction Assemblies references without owning — CA-OBJ-011 is a shell pointing at shared identity | identity lives at foundation; Assemblies adds respondent-identity/member-identity classes (extension) |
| Organisations | required shared contract | bodies referenced by ReceivingAuthority, commissioner, operators | plain reference suffices |
| Geography | required shared contract | jurisdiction/locality references on Institution + population rules | needs frame-coverage extension — geography alone isn’t coverage |
| Roles | required shared contract | role vocabularies for actors (operator, facilitator, member, secretariat) | assembly-specific roles extend a shared role base |
| Institutional authority | unresolved cross-component contract | CA-OBJ-030 AuthorityArtefact is Assemblies-shaped; whether a shared authority-object contract exists is undecided | if CORE gains a generic authority model, Assemblies artefacts should conform — joint design needed |
| Technical permissions | required shared contract | permission checks separate from authority (dual attribution) | foundation authN/authZ is expected; Assemblies adds the authority layer on top |
| Provenance | required shared contract | event provenance fields (actor, authority, source, digest) | Assemblies strengthens to dual-attribution + append-only (extension) |
| Audit | required shared contract | event-recording capability | append-only semantics + ceremony bundles are Assemblies extensions |
| Documents/evidence references | required shared contract | blob/document refs with digest pinning | Assemblies adds register-level governance (balance, disclosure) as extension |
Boundary rules
- Assemblies consumes foundation contracts where they exist; it does not replicate identity/permissions/documents.
- 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.
- Nothing in the foundation may write canonical Assemblies records — the ownership boundary in
OWNERSHIP-BOUNDARIES.mdapplies to sibling components too. - This record does not assert anything about CORE’s current state; verification of actual CORE capability is a later cross-component task.