Link to current text
A.19.CHR:4.3.2 - Guards and gate separation
- Guard decision tristate: mechanism‑level guards return
GuardDecision := {pass | degrade | abstain}.
- Unknown never coerces to pass: unknown/insufficient evidence MUST map to
degrade or abstain, not to pass.
- Gate decision separation: mechanisms and suite objects MUST NOT publish
GateDecision nor DecisionLog. block is gate‑only (OperationalGate(profile)).
- Guard lexeme reservations:
USM.CompareGuard / USM.LaunchGuard are gate‑level pins; mechanism predicates use suffixes …Admissibility / …Eligibility.