Stage 2.6A-FIX QT-001 Machine-Enforced Tier/Plan/Signoff + Hardcode Guards — Readme First
Stage 2.6A-FIX — Readme First
Status: PASS. Mode: EXECUTION (principal-delegate). Live mutation: YES — additive, reversible, birth-neutral. NO QT-001 apply. NO permit. NO trigger/gateway-body/writer-execute change. MCP read-back PASS.
This macro corrects the FAILED Stage 2.6A. Codex independent audit returned STAGE2_6A_FAIL_HARDCODE_STILL_DANGEROUS. We reproduced all nine findings live, then fixed them so the Plan/Tier/Signoff layer is machine-enforced and auditable. We did NOT proceed to 2.6B, did NOT open permits, did NOT apply.
From: STAGE2_6A_FAIL_HARDCODE_STILL_DANGEROUS To: STAGE2_6A_MACHINE_ENFORCED_PLAN_TIER_SIGNOFF_LAYER_READY_FOR_INDEPENDENT_REAUDIT
Headline
Tier classification is now derived from DATA + machine-readable predicate rules (qt001_tier_rule_registry) evaluated by a pure operator interpreter (fn_qt001_eval_tier_predicate) — the CASE was removed from fn_qt001_build_plan_registry and the hardcoded 5-collection IN-list removed from fn_qt001_refresh_plan_snapshot. Because TIER1 now requires a signoff BOUND to the current plan checksum (none exists), the five collections previously hard-listed as TIER1 are correctly DEMOTED to TIER2. Machine result: TIER1=0, TIER2=7, TIER3=6. Nothing is apply-allowed; readiness v4 is BLOCKED for the right reasons.
Documents
01 codex-failure-reverification; 02 machine-enforced-tier-rules; 03 parity-signal-not-authority; 04 plan-bound-signoff; 05 computed-blocked-reasons; 06 hardcode-guard-v2; 07 readiness-v4; 08 writer-public-bypass-visibility; 09 safety-audit; 10 design-index-update; 11 final-summary; 12 gpt-mcp-readable-checkpoint.
Verdict
PASS. Fresh independent Codex re-audit required BEFORE any Stage 2.6B work, permit, or apply.