A.19.CHR:9 - Consequences

Consequence	Upside	Cost / risk	Mitigation
Shared CHR contracts across uses	A later comparison can recover the same member declarations and joint conditions	Resolving the declarations and their editions takes effort	Reuse the baseline while its contracts and intended use remain applicable; keep method-specific choices in their governing descriptions
Explicit P2W planned baseline	Eliminates hidden slot filling and improves auditability of editions, time selectors, and crossings	Adds a planning plan item per path slice	Keep the plan item minimal (refs and pins only) and project it to views for readability when needed
Tri-state guard semantics	Avoids false precision and prevents unknown from silently passing	More conservative behavior can yield larger selected sets or more abstentions	Use explicit SoS‑LOG degrade branches for probe-only exploration while preserving traceability
Spec pins, not copied spec content	Reduces drift and keeps CN‑Spec/CG‑Spec as real centers of gravity	Requires discipline in authoring and review	Enforce “refs-only” at suite/plan level and use conformance items CC‑A67CHR‑3 and CC‑A67CHR‑13 to keep the surface clean