prj-forgejo-org-refactor/decisions/rollback-gate-amendment.md
tegwick 3bd576990b Refine stewardship evidence and specify owner preparation handoffs
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e782-9f45-7382-afff-77ad665b88ec
2026-09-28 13:06:18 +02:00

53 lines
2.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Proposed amendment: allow the prerequisite proof to be produced
Status: proposed; not enacted. Decision:
`e9aca79b-f167-4326-94cd-037dcea34cd2`.
## Problem
The standing rule requires all four entry conditions before T03/T04, while T04
was intended to produce condition 4. Unrelated application rollback receipts do
not resolve this dependency. Moving the same experiment to another repo merely
to evade the gate would not resolve it either.
## Exact proposed rule
Replace the all-four prerequisite for the **disposable-only portions of T03/T04**
with these conditions:
1. Entry conditions 1–3 are met and the evidence is accepted for the tested scope.
2. railiance-forge has a file-backed, separately authorized rehearsal record
naming an isolated disposable instance, its product/version/configuration,
fixtures, permitted operations, cleanup and rollback evidence.
3. The rehearsal uses no existing production org/repository/package, customer
data or production credential grant. Its GitOps and image-pull consumer is a
disposable fixture. Configuration differences from production are recorded.
4. Only disposable repo transfer/rename, package behavior and recovery are
exercised. No existing repo is used merely because it seems low-stakes.
5. T03/T04 evidence may satisfy condition 4 only for behavior reproduced with
equivalent relevant configuration; untested production-specific differences
remain blockers. The forge owner signs off applicability.
**All four entry conditions remain required before any production transfer,
production rehearsal, or T05 execution.** G3/G4 still need accepted behavior and
rollback evidence; production GitOps and fresh-pull acceptance remain required
before migration completion. This amendment changes sequencing, not evidence
quality or production authority.
## Files to change if accepted
- AGENTS.md, “Before anything else”: keep the all-four production rule and add
the exact disposable-only exception above for T03/T04.
- ORGREF-WP-0001 entry gate: reference the exception and keep conditions 1–4.
- T03/T04: distinguish disposable prerequisite proof from later production
applicability verification; remove the requirement for prior condition-4
proof only from the disposable portion.
- GOAL.md/history and State Hub decision: record the accepted amendment and
its scope. Do not mark any gate green merely because this rule is accepted.
## Effect today
None on execution readiness: conditions 2 and 3 still fail, and no owner
rehearsal record/target has been authorized. Accepting this proposal alone would
not permit any live action now. Until explicitly accepted, AGENTS.md and the
original all-four rule remain unchanged.