golden waiver: issued 2026-10-07, expires 2026-10-13 — controller 0.302.0 delivered by floor the day after the 0.301.0 bake; weekly bake due 2026-10-13

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-07 09:29:15 +02:00
parent 011a481a32
commit 9828acc646
1 changed files with 14 additions and 0 deletions
@@ -0,0 +1,14 @@
+# documentation/tests/golden-waiver.yml — read by scripts/golden_currency_gate.py
+#
+# Goldens are on a CADENCE, not per release (operator ruling 2026-09-13, R-468): weekly, and always
+# before any drill or fresh install. While this waiver is valid a golden BEHIND the record makes the
+# gate ADVISORY instead of red. It never covers a golden that is UNRECORDED (R-385). At most 14 days
+# after `issued`, or the gate refuses it. Renew with a new dated commit; delete it at the first
+# external install.
+# Issued 2026-10-07 by CC: controller 0.302.0 was released and delivered by floor (operator ruling, `09` §3 decision 161)
+# the day after the 0.301.0 bake (2026-10-06); the weekly bake is due 2026-10-13. No drill or fresh install is planned
+# before then. Not a bypass: dated, capped at the weekly due date.
+issued: 2026-10-07
+expires: 2026-10-13
+reason: pre-customer development; goldens on a weekly cadence (operator ruling 2026-09-13)
+register_row: R-468