Skip to content

STD-GOV-002: Exceptions, Waivers & Risk Acceptance

1. Context

Sometimes, for speed or survival, we must break the law. This standard defines how to do so without destroying the system's integrity. "If you break it, you sign for it."

2. The Standard (The Floor)

  • [MUST] The Variance Permit (Waiver): Violating a [MUST] clause REQUIRES a recorded Waiver.
  • Location: documentation/05_operations/waivers/[ID]_[Standard]_[Reason].md
  • Content: "Why we are breaking it", "What is the Risk", "When will we fix it (Expiry)".
  • [MUST] Risk Acceptance: The Governance Lead (or Product Owner) MUST explicitly sign off on the risk.
  • [MUST] Expiry: Every Waiver MUST have a ReviewDate. Waivers are not permanent.

3. Best Practices (The Path)

  • [SHOULD] Tech Debt Labeling: Code implementing a waiver should be commented with // WAIVER: [ID] - Expires [Date].
  • [SHOULD] cleanup: When the expiry hits, the Waiver is either Renewed (Risk Re-Accepted) or the Code is Fixed (Standard Enforced).

5. Version History

Version Date Author Change
1.0 2026-01-25 AI Established Waiver Protocol

Version History

Version Date Author Change
0.1.0 2026-01-26 Antigravity Initial Audit & Metadata Injection