[IMP-20-RUNTIME][DEFERRED] Implement Phase Z frame contract validator when §A5 gate is satisfied #55

New Issue

Kyeongmin · 2026-05-20T00:22:03+09:00

Kyeongmin commented

2026-05-20 00:22:03 +09:00

Purpose

Track the runtime implementation deferred by #20.

Issue #20 was closed as a documented-axis/reference-only issue. It created:

docs/architecture/IMP-20-FRAME-CONTRACT-VALIDATION-REFERENCE.md

However, #20 did not implement a Phase Z runtime validator.

Source

#20 IMP-20 H2 frame contract validation
docs/architecture/IMP-20-FRAME-CONTRACT-VALIDATION-REFERENCE.md
Section A5 re-activation gate

Runtime Status

RUNTIME_DEFERRED.

No runtime implementation is required until the A5 activation gate is satisfied.

Activation Gate

Implement this only when all of the following are true:

Step 10 partial emit is insufficient for a concrete regression.
There is failing evidence:
- failing MDX or scenario
- step10_frame_contract.json
- final.html slot-path excerpt
IMP-04/catalog owner confirms catalog tightening alone cannot resolve it.

Scope When Activated

Implement a Phase Z-owned frame_id × sub_zone validator.
Validate against Phase Z frame contract vocabulary.
Use Phase Z-owned pattern dict design.
Preserve Step 10 / Step 18 boundary from the reference doc.

Guardrails

Do not import or reuse Phase Q REQUIRED_PATTERNS.
Do not use Phase Q area names (body_bg, body_core, sidebar, footer) as Phase Z validator keys.
Do not modify src/content_verifier.py.
Do not promote WIP catalog/template work from IMP-04.
No AI/Kei normal-path behavior.

Acceptance Criteria

Runtime implementation only starts after the activation gate is proven.
If gate is not satisfied, this issue remains dormant.
Future work can find this runtime follow-up without reading #20 docs manually.

## Purpose Track the runtime implementation deferred by #20. Issue #20 was closed as a documented-axis/reference-only issue. It created: - `docs/architecture/IMP-20-FRAME-CONTRACT-VALIDATION-REFERENCE.md` However, #20 did not implement a Phase Z runtime validator. ## Source - #20 IMP-20 H2 frame contract validation - `docs/architecture/IMP-20-FRAME-CONTRACT-VALIDATION-REFERENCE.md` - Section A5 re-activation gate ## Runtime Status RUNTIME_DEFERRED. No runtime implementation is required until the A5 activation gate is satisfied. ## Activation Gate Implement this only when all of the following are true: 1. Step 10 partial emit is insufficient for a concrete regression. 2. There is failing evidence: - failing MDX or scenario - `step10_frame_contract.json` - `final.html` slot-path excerpt 3. IMP-04/catalog owner confirms catalog tightening alone cannot resolve it. ## Scope When Activated - Implement a Phase Z-owned `frame_id × sub_zone` validator. - Validate against Phase Z frame contract vocabulary. - Use Phase Z-owned pattern dict design. - Preserve Step 10 / Step 18 boundary from the reference doc. ## Guardrails - Do not import or reuse Phase Q `REQUIRED_PATTERNS`. - Do not use Phase Q area names (`body_bg`, `body_core`, `sidebar`, `footer`) as Phase Z validator keys. - Do not modify `src/content_verifier.py`. - Do not promote WIP catalog/template work from IMP-04. - No AI/Kei normal-path behavior. ## Acceptance Criteria - Runtime implementation only starts after the activation gate is proven. - If gate is not satisfied, this issue remains dormant. - Future work can find this runtime follow-up without reading #20 docs manually.

Kyeongmin commented

2026-05-20 00:22:11 +09:00

Follow-up tracking issue created for deferred runtime implementation:

[IMP-20-RUNTIME][DEFERRED] Implement Phase Z frame contract validator when §A5 gate is satisfied

#20 remains closed as documented-axis/reference-only. Runtime implementation is explicitly deferred and tracked separately.

Follow-up tracking issue created for deferred runtime implementation: - [IMP-20-RUNTIME][DEFERRED] Implement Phase Z frame contract validator when §A5 gate is satisfied #20 remains closed as documented-axis/reference-only. Runtime implementation is explicitly deferred and tracked separately.