Research / architecture

Current research

CA-A1 — agenda and remit contract

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/AGENDA-REMIT-CONTRACT.md

architectureagendaremit

Sources: SRC-0038SRC-0048SRC-0070SRC-0100

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)

AgendaItem (CA-OBJ-015)

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

  1. Editing agenda text is a permission; approving/amending an agenda is authority — the two never merge (CA-REQ-080).
  2. Every agenda change mid-cycle creates a versioned event with authority + reason — silent remit drift is impossible by construction.
  3. “No agenda items” is a representable institution state (some models defer agenda to members — Pattern B).
  4. Question wording is preserved verbatim — paraphrase is a new version.

Sources