01.2 — Quorum
Committee + cadence
infrastructure for
healthcare institutions.
Most institutions already have meetings. What they lack is operationalised governance continuity — proof that obligations were registered, considered, discharged, and recorded by people with the authority to act. Quorum is the infrastructure that makes governance continuity producible.
A — What Quorum is
The governance-continuity substrate.
Cadence creates governance acts — incidents, complaints, audits, decisions. Quorum is the layer that asks whether the right people, with the right authority, considered those acts at the right time, in a quorate forum. It handles the infrastructure that institutions traditionally run from a binder: who is on which committee, in what membership type, until when, with what authority to bind the institution.
- 01
Chronology
An append-only governance event substrate with reservation partition and an immutability trigger at the database. Every governance act has a recorded provenance; corrections are amendment events, never edits.
- 02
Identity
Persons, Roles, and Role Holdings — institutional identity that exists in the chronology before any auth account is bound. Closed holdings persist alongside open ones for deterministic capacity reconstruction.
- 03
Committees + Terms of Reference
Constitutive and scrutinising authority. Top-level vs sub-committee asymmetry enforced. ToR approvals emit chronology events and supersede prior versions; superseded rows persist.
- 04
Scheme of Delegation
Decisional authority. Delegations from source bodies to recipients (committees, posts, individuals) with limits, conditions, reservations, sub-delegation terms. Approval emits SchemeAmended; the institutional timeline has no gap.
- 05
Memberships
Persons bound to Committees in declared Membership Types for an effective period. Three end events for three doctrinally distinct end reasons. Closed memberships persist.
- 06
Obligation calendar
Forward calendar of governance obligation registered against committees with target windows. Overdue computed at query time from past target window plus pending state — visibility without state mutation.
- 07
Meetings, agendas, items
Per-meeting flow: schedule → draft items → construct agenda → convene with recorded quorum state → close. The first three governance acts in the lifecycle each emit chronology events that bind the items they produced.
B — Why this is a separate product
Quorum and Cadence are doctrinally distinct.
Cadence and Quorum sit alongside each other, not above or below. Cadence handles the operational reality of governance work — the queue of incidents to triage, the audit cycles to close, the policies to keep current. Quorum handles the constitutional reality — the committees that hold authority, the scheme that delegates it, the memberships that confer capacity, the meetings in which authority is exercised.
The two are visually related, doctrinally aligned, semantically consistent — and deliberately not feature-coupled. Quorum does not import Cadence's schemas; Cadence does not call Quorum's APIs. Each system is buildable, deployable, and comprehensible on its own. A practice that wants only one of them gets only one of them; a practice that wants both gets the doctrinal consistency that comes from a shared backbone, not the feature interlock that creates upgrade-path lock-in.
C — What 'substrate' means here
Buildable. Type-checked. Not yet a product surface.
The substrate primitives above — chronology, identity, committees + terms of reference, scheme of delegation, memberships, the obligation calendar, meetings and agendas — are implemented, tested, and migration-ready. They cover what an institution needs to write into the chronology to make subsequent governance work defensible.
What's not yet present is the user-facing governance domain that runs on top of them — the screens an administrator uses to register a committee, draft an agenda, record a meeting's quorum state, project the obligation calendar. Those land next, in the same cadence-and-calibration approach Cadence followed: build, ship to a partner, listen, refine.
Item consideration and outcomes (which discharge obligations), per-item attendance, capacity assertion, conflicts and recusals, submissions, and minutes are the upcoming substrate slices before the user-facing surface opens to partners.