Governance Bodies & Commissions

The domain is built around three documents. A Commission carries a typed scope (CommissionScope: jurisdiction × authority_level × authority_areas × reports_to) and binds members through CommissionMembership entries that hold a role (chair, deputy, member, secretary), term dates and rotation metadata. A Meeting hangs underneath with agenda items, minutes and Decision children.

A GovernanceAuditLog records every mutating call as an append-only row scoped strictly to the tenant. The /commissions router exposes CRUD plus filters on type/status/jurisdiction/authority_level and a /commissions/{id}/rotation-report that combines term_limit_months, max_consecutive_terms, rotation_policy and a 120-day gap-reset rule to surface members whose mandate is about to expire or who are blocked from another consecutive term. Member CRUD includes structured ConflictOfInterestDeclaration objects with a typed lifecycle (declared → acknowledged → recused → resolved); /commissions/{id}/conflicts lists across the commission so the chair can vet upcoming votes.

Meetings move through their agenda; when a Decision is created it starts as draft, transitions through adopted → published → rescinded, captures the vote split (for/against/abstain), and is auto-stamped with a {YYYY}-{NNN} reference number. Once published, the decision is queryable across all meetings via /meetings/published/decisions, which is what feeds the public regulatory feed and ties back to F01.04 rule changes. Every write — commission create/update, member add/remove, conflict declaration, decision lifecycle transition — appends a GovernanceAuditLog row that the read-only /governance/audit router exposes with filters and a /governance/audit/actions taxonomy.

Tenant isolation is enforced at the model layer: an FFPJP secretary can never see SBF audit traffic, even via the audit router.