Agenda and remit contract
CA-A1 architecture record. Updated: 2026-10-05. Agenda authority is recorded separately from software permission (CA-REQ-036; AUTHORITY-MODEL).
Remit (CA-OBJ-014)
id,cycle_id,version,authority_ref— who set it (commissioner / elected body / statute / members / public-vote / mixed)scope_statement,question_list,boundary_conditions(in/out of scope declarations)legal_constraints,amendment_policy(can remit change mid-cycle? by whom?)- versions immutable; amendment → new version linked to prior
AgendaItem (CA-OBJ-015)
id,remit_ref,order,title,wording(exact question text)proposer(actor + the channel: member / public petition / council motion / commissioner)approver+authority_ref— the approval is an event with basisinclusion_reason/exclusion_reason— rejected proposals keep exclusion reasons recorded (CA-REQ-037)public_input_refs— linkage to mass-input channel records where the item originated in public participationmember_proposal_refs— linkage where members generated the itemstatus(proposed / approved / rejected / deferred / amended / withdrawn)amendment_of— version chain; historical versions immutable
Channel linkage
ExternalChannel (CA-OBJ-031) records mass-input origins (e.g. a petition threshold crossed, a public-vote result). AgendaItems cite channel records — the channel’s bias label travels with the reference so public-origin items are never confused with commissioned remit.
Boundary rules
- Editing agenda text is a permission; approving/amending an agenda is authority — the two never merge (CA-REQ-080).
- Every agenda change mid-cycle creates a versioned event with authority + reason — silent remit drift is impossible by construction.
- “No agenda items” is a representable institution state (some models defer agenda to members — Pattern B).
- Question wording is preserved verbatim — paraphrase is a new version.