admin
a23ae9e3dc
gates / gates (push) Successful in 28s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
17 lines
1.2 KiB
YAML
17 lines
1.2 KiB
YAML
# 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 AFTER the 0.236.0 bake landed — not over a bake that could have been done.
|
|
# Renewed 2026-09-27 by CC for 7 days only: the version-travel brief said "no golden" this session, and the
|
|
# weekly bake (last: 0.258.0, 2026-09-20) is DUE — STATUS asks the operator for it. Not a bypass: dated, capped.
|
|
# Renewed 2026-10-04 by CC for 3 days only: the guest-OS-lane brief releases controller 0.291.0 and agent 0.140.0
|
|
# and ENDS with a golden bake + vouch (its Part H); this covers the hours between the release and that bake. Not a
|
|
# bypass: dated, capped, and the bake is in the same session.
|
|
issued: 2026-10-04
|
|
expires: 2026-10-07
|
|
reason: pre-customer development; goldens on a weekly cadence (operator ruling 2026-09-13)
|
|
register_row: R-468
|