Research / architecture

Current research

CA-A1 — population, frame and invitation model

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/POPULATION-AND-INVITATION.md

architecturepopulationinvitation

Sources: SRC-0038SRC-0047SRC-0120SRC-0122

Population, frame and invitation model

CA-A1 architecture record. Updated: 2026-10-05. Do not store electoral registers in this architecture by default — references and controlled imports only.

Objects

EligiblePopulationRule (CA-OBJ-004)

InvitationFrame (CA-OBJ-005)

InvitationCampaign (CA-OBJ-006)

RespondentPoolRef (CA-OBJ-007)

Key architectural decisions

  1. Frame data never defaults into Cicada. The canonical objects are descriptors + digests + coverage statements. If an implementation needs imported rows, that is an explicit per-field decision with privacy_class consequences — not an ambient property of the model.
  2. Duplicate prevention is expressed as a declared rule (dedupe_policy on the pool: person-key, address-key, household-key) executed at custody — Cicada records the policy and its outcome counts, not the matching keys.
  3. Non-response is first-class: the funnel stores nonresponse as an analytic state — it is evidence for stratification-review, not noise.
  4. Weighting is declared, not hidden: invitation weighting lives on the frame/campaign records so “equal invitation probability” claims are checkable.
  5. Respondent ≠ member: pool records and membership records never merge; selection is a crossing event recorded in the Membership + SelectionRun, so pool retention can burn down independently.

Sources