06 — Writer Remains Blocked + Enforcement Contract (SUPERTRACK F)

The writer was not modified in Stage 2.6A (no execute-path change, additive/reversible only). Instead this layer defines the enforcement contract the next layer must wire in, and proves the writer cannot execute on hardcoded assumptions now.

Objects

• v_qt001_writer_registry_enforcement_contract — the preconditions the writer MUST verify before execute, each with current_value, satisfied, and enforced_in_writer.
• v_qt001_writer_must_remain_blocked_guard — asserts the writer cannot currently execute via any path.

Enforcement contract (preconditions)

precondition	source registry	satisfied now	enforced_in_writer
plan_bound_and_current	qt001_plan_registry	true (13 current rows)	false
tier_apply_allowed	qt001_tier_registry	false	false
independent_signoff_safe	qt001_independent_review_signoff	false	false
owner_execute_permit_bound	birth_admission_permit_v2	false (0 open)	false
scale_safe	v_qt001_scale_not_safe_guard	false	false

enforced_in_writer = false for all five — the live writer fn_dot_birth_qt001_apply does not yet read these registries. That wiring (making the writer read plan checksum / tier apply_allowed / signoff SAFE / permit binding) is a NEXT-layer task and must be done stricter and rollback-safe.

Must-remain-blocked guard

v_qt001_writer_must_remain_blocked_guard.pass = true. Components: open_execute_permits 0, any_tier_permits_apply false, signoff_safe false, qt001_apply_origin_births 0, writer_unwired_so_cannot_trust_old_path true. Even though the writer is unwired, it cannot execute because (a) its p_execute defaults false, (b) it fail-closes without a valid open execute permit (0 exist), and (c) no tier permits apply and signoff is NOT_SAFE.

Why not patch the writer now

Stage 2.6A's mandate is plan/tier/signoff SSOT + hardcode elimination only. Wiring the writer to the registries belongs with the permit/run/keyset layer so it can also enforce permit checksum/watermark binding atomically. Patching it here in isolation would add an execute-path change without the permit lifecycle it must bind to — out of scope and riskier. The contract view records exactly what that layer must implement.