# 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-13 by CC: controller 0.310.0 (R-998, „A gép kikapcsolása") was released the evening of the weekly bake
# (golden 0.309.0, baked 2026-10-13); the next weekly bake is due 2026-10-20. The bake and its vouch are the operator's
# acts (the R-998 task fences them). No drill or fresh install is planned before then. Not a bypass: dated, capped at
# the weekly due date.
# 2026-10-14: goldens 0.310.0 and 0.311.0 were baked the same day (`golden-0.311.0-2026-10-14/`), so the golden is at
# the newest controller and this waiver covers nothing today. It stays until its date for a release before the next bake.
issued: 2026-10-13
expires: 2026-10-20
reason: pre-customer development; goldens on a weekly cadence (operator ruling 2026-09-13)
register_row: R-468