What problem does it solve?
It helps you verify that the model-filled “operation mode” in Stage 4 output is specific, non-placeholder, and consistent with the originating HARA scenario, without re-evaluating safety target semantics.
Core Features & Use Cases
- Stage4 “操作模式” targeted review: Checks that “操作模式” is present, not a placeholder, and is a mode name rather than a long scene description.
- Evidence-aligned consistency checks: Ensures the chosen mode aligns with the originating scenario described in Comments, referencing Stage3 HARA only for the relevant MF_ID when needed.
- Guardrail-driven validation & repair: Runs Stage4 machine validation first, then allows controlled fixes that update only the “操作模式” field before exporting merge-ready results.
Quick Start
Ask the system to run Stage 4 machine validation and review the operation mode for output/<RUN_ID>_stage4_sg_sum.json, updating only the “操作模式” field if required.