Framework v7.9 — Promotion Release: 3 Advisory Gates → Enforced via Single-Flag Flip After 14-Day Calibration

v7.9 shipped 2026-05-21 via FT2 PR #417 (ea53ff4). A single-line edit at scripts/check-state-schema.py:132 (BRANCH_ISOLATION_ADVISORY_MODE True to False) promoted 3 v7.8.1 advisory gates simultaneously: BRANCH_ISOLATION_VIOLATION Mode B (infra commit-level), Mode C (per-state.json mutation), and FEATURE_CLOSURE_COMPLETENESS (write-time). All four section 2.2 promotion criteria were met against 14-day Mechanism A telemetry (18 + 13 + 13 firings, 0 zero-candidate rows, 0 false positives). First real-world Mode C gate fire was caught + resolved in the same session — the post-merge close-out commit hit the merged-dead feature/v7-9-promotion branch declaration; resolved via 1-line state.json::branch field update. Total framework mechanisms post-promotion 37 mechanical gates plus 5 advisories. Reversibility is single-line revert in under 5 min. Phase E validation soak ran 2026-05-21 through 2026-06-04. Section 99 synthesis is complete: all 3 kill criteria not_fired (verdict PASSED, evaluated 2026-05-28 post-B2 baseline); the promotion holds and the feature is complete.

Framework v7.9 — Promotion Release

Synthesized slot. Full case study lives upstream at docs/case-studies/framework-v7-9-promotion-case-study.md. This MDX is the showcase index entry. Section 99 synthesis is complete: all 3 kill criteria not_fired (verdict PASSED, evaluated 2026-05-28 post-B2 baseline). The promotion holds and the feature is complete.

What v7.9 shipped (one paragraph)

A single-line edit at scripts/check-state-schema.py:132 flipped 3 v7.8.1 advisory gates to enforced simultaneously: BRANCH_ISOLATION_VIOLATION Mode B (infra commit-level) + Mode C (per-state.json mutation) + FEATURE_CLOSURE_COMPLETENESS (write-time). All four section 2.2 promotion criteria met against 14-day Mechanism A telemetry. First real-world Mode C gate fire caught + resolved in the same session. Total framework mechanisms post-promotion: 37 mechanical gates + 5 advisories.

Why this matters

v7.9 is the first framework version that used Mechanism A telemetry as a gate on its own promotion decision. FT2-FH-001 and FT2-FH-002 captured silent-pass incidents at v7.7 and v7.8.3 respectively. FT2-FH-003 (added 2026-05-21) is the first honesty-ledger entry that is NOT a correction — it codifies the calibration discipline the framework used to AVOID a silent-pass at v7.9.

Cross-references

Upstream case study (FT2): docs/case-studies/framework-v7-9-promotion-case-study.md
Cold-start entrypoint: .claude/entrypoints/framework-v7-9.md
Honesty ledger FT2-FH-003: framework-honesty-ledger.md#ft2-fh-003
Infra master plan section 3.6.2: infra-master-plan-2026-05-12.md
v7.9 candidates spec: 2026-05-08-framework-v7-9-candidates.md

Phase E calendar (2026-05-21 through 2026-06-04)

2026-05-21: v7.9 shipped (this commit)
2026-05-22: B11 UCC hardening T+3d check + product feature work resumes
2026-05-23: B8 parent UCC T+7d kill-criteria + HADF Phase 2-bis Sub-exp 1 launch
2026-05-27: B12 UCC hardening T+7d advance to complete
2026-05-28: B2 post-v7.9 baseline snapshot + B9 Part 8 eligibility + section 99 synthesis lands here
~2026-06-04: Phase E exit + v7.9.1 build window opens

Status

complete — Section 99 synthesis is done. All 3 kill criteria evaluated not_fired on 2026-05-28 (Phase E Day 7, post-B2 baseline): K1 (0% Mech A coverage at decision) not_fired — 18 + 13 + 13 firings observed; K2 (>5% false-positive rate) not_fired — 0/44 firings; K3 (rollback within T+7d) not_fired — no rollback PR, advisory mode still False on main. Verdict: PASSED — v7.9 promotion holds. The adoption-percentage deltas surfaced by make integrity-diff are denominator-dilution process regressions (Phase E features added without adoption-metric backfill), not v7.9-caused — filed as a v7.9.1 backfill follow-up.