Policy Paper Style
April 17, 2026 · View on GitHub
Style: Formal document tone, muted charcoal, sober blue accents, governance-first readability Best for: Governance notes, internal rules, policy explainers, operational guidance, legal-adjacent summaries
Style Characteristics
| Property | Value |
|---|---|
| Background | Paper white #fbfbf9 |
| Text | Charcoal #25272b |
| Accent | Rule blue #46648f |
| Secondary | Policy gray #5f6772 |
| Muted | Archive gray #848b94 |
| Tint | rgba(70,100,143,0.05) |
| Title Font | Noto Serif SC, Georgia, serif |
| Body Font | Inter, Noto Sans SC, sans-serif |
| Surface | Quiet, memo-like, restrained |
Template
Exceptions Should Be Documented Before They Are Operationalized
Most policy debt is created when teams treat urgent operational exceptions as temporary, then silently normalize them. This revision makes approval, duration, and owner requirements explicit before any exception enters live practice.
Temporary behavior becomes permanent unless policy names the boundary first
Policy Change
All production exceptions now require defined expiry dates, documented rationale, and named approvers, with monthly review until closure.
30d
Maximum default exception term