1. Proposal
An owner opens an RFC with scope, affected users, and draft safeguards.
Governance process
Public governance receipts for RFCs, decision records, releases, and quarterly accountability updates.
Governance receipts
Every governance claim links to an artifact.
This page exposes active RFCs, decision owners, and release links so contributors can audit process, not just summaries.
Process
RFC lifecycle
A shared lifecycle keeps policy changes reviewable, attributable, and linked to release artifacts.
2. Review window
Reviewer roles assess harms, rollback plans, and implementation fit during a dated comment window.
3. Decision
A named owner records outcome and rationale in the decision log with clear follow-up responsibilities.
4. Release
Accepted changes ship with a linked release/version so downstream teams can verify what changed and when.
Current work
Current/open RFCs
Open RFCs show the status, owners, reviewer roles, and active review windows before decisions are logged.
Status: review
RFC-2026-02: Evidence-pack compatibility baseline
Defines a minimum compatibility contract for evidence packs so diagnostics and standards pages can share structured receipts.
Opened: 2026-02-03
Review window: 2026-02-03 → 2026-02-24
Owner: Institute steward council
Reviewer roles: Studio facilitator, Operations lead, Documentation steward
Status: proposal
RFC-2026-01: Recourse escalation SLA for diagnostics
Sets response-time targets and ownership for contested diagnostic outcomes.
Opened: 2026-01-28
Review window: 2026-01-28 → 2026-02-20
Owner: Program operations
Reviewer roles: Risk steward, Community reviewer
Receipts
Decision log
Every decision includes date, accountable owner, rationale, and release linkage.
Accepted • 2026-02-14
DEC-2026-02-01: Adopt decision-owner field for all governance records
Ownership was inconsistent across forum outputs. Mandatory owner attribution reduces ambiguity in follow-up.
Owner: Institute steward council
Linked release: governance-v1.4.0Accepted with amendment • 2026-01-22
DEC-2026-01-03: Extend review windows to include community office hours
Asynchronous review missed context from implementation teams; office-hours notes now count as formal review input.
Owner: Program operations
Linked release: governance-v1.3.2Accepted • 2025-12-19
DEC-2025-12-02: Archive inactive RFC threads after release
Open threads without closure dates made audits hard. Archiving after release keeps status visible and history navigable.
Owner: Documentation steward
Linked release: governance-v1.2.0Quarterly notes
Quarterly governance updates
Dated updates summarize what shipped in governance operations each quarter.
2026-01-15
Q4 2025 governance update
Published 3 decision records, closed 2 RFCs, and linked all accepted decisions to release versions.
2025-10-10
Q3 2025 governance update
Introduced reviewer-role tracking in RFC metadata and expanded open forum participation hours.
2025-07-12
Q2 2025 governance update
Established the baseline RFC lifecycle and started publishing dated decision receipts publicly.