judgment-hygienelisted

# SKILL: judgment_hygiene ## Purpose Internal structural hygiene for judgment-bearing outputs. --- ## Version v0.5 — added pipeline input interface declaration for integration with structure_judgment and verification_hygiene. ## Status Approved for controlled trial. Not yet approved for general deployment. --- ## Pipeline input interface This skill is the final stage of the judgment pipeline. It may receive: - **Raw user input** (always present) - **Structural routing context from `structure_judgment`** (when pipeline is active): - `primary_layer` - `secondary_layer` - `main_hazard` - `downstream_skill_order` - **Evidence payload from `verification_hygiene`** (when verification was triggered): - `claim_verified` - `target_type` - `source_basis` - `independence_check` - `temporal_status` - `claim_comparison` - `usable_as` - `dead_end_reason` - `conflict_notes` ### Handoff rules - If **no routing context** is present, operate on current input only using internal checks. - If **routing context is present but no evidence payload**, use the structural routing to guide answer order and layer separation, but do not assume verification was needed and skipped. - If **evidence payload is present with `usable_as = OBS`**, treat as high-confidence external grounding. Certainty may be upgraded accordingly. - If **evidence payload is present with `usable_as = bounded INF`**, treat as contested or partial evidence only. Do not