Skip to content

Exempt faithful preserve-by-default splits from the pre-merge gate#165

Merged
LuminLynx merged 1 commit into
mainfrom
claude/gate-exempt-preserve-splits
May 21, 2026
Merged

Exempt faithful preserve-by-default splits from the pre-merge gate#165
LuminLynx merged 1 commit into
mainfrom
claude/gate-exempt-preserve-splits

Conversation

@LuminLynx
Copy link
Copy Markdown
Owner

Summary

Records the decision to skip pre-merge gate runs for faithful preserve-by-default splits, so the revision is deliberate and documented rather than silent drift.

What changed

  • docs/REGRESSION_GATE.md — new section "When the pre-merge gate is required vs. optional":
    • Required for any change that realigns expected values, or any new authoring.
    • Optional (informational) for a faithful preserve-by-default split (structural c2-split redistributing locked old-c2=Tc2=T+c3=T, zero realignments) — it can't change any expected value, so the gate would only produce a calibration snapshot. Local validators + the faithful decomposition suffice.
  • docs/RUBRIC_AUDIT.md — one-line note on the locked "regression backfill" bullet pointing to the narrowed rule, so the two docs don't contradict.

Why

The original "always gate before merge" rule predated the grader/gold-standard principle (PR #161). Its purpose was to catch grader miscalibration we'd act on; under preserve-by-default we don't act on grader output, so that purpose doesn't apply to these mechanical splits. Recording it avoids the silent-drift failure mode that produced the un-gated PR #146.

Test plan

  • Docs render; no contradiction between the two docs.
  • Founder review of the required-vs-optional line.

After this lands: Units 7–9 proceed as faithful preserve-by-default splits, no gate runs.


Generated by Claude Code

Narrows the locked 'full regression re-run before merge' rule
(RUBRIC_AUDIT.md / REGRESSION_GATE.md). A faithful preserve-by-default
split — structural c2-split that only redistributes a locked
old-c2=T into c2=T+c3=T, with zero realignments — is exempt: it
changes no locked value's meaning, and since we don't act on grader
output, a gate run can't change any expected value (it would only
produce an informational Sonnet-calibration snapshot). Local
validators + the faithful decomposition suffice.

Gate stays REQUIRED for any change that realigns expected values or
any new authoring. Recorded to avoid silent process drift (the kind
that bit PR #146).
@LuminLynx LuminLynx merged commit d57f27a into main May 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants