When CPCR cannot safely compute a full conflict resolution, it returns standardized refusal states instead of fabricating certainty.
These states may appear in:
- the Ethical Risk Index for a case, and/or
- the
refusal_statefield of the CPCR conflict record.
Used when one or more required variables are missing, incomplete, or withheld.
- Example causes:
- No externality ledger for physical impacts.
- Opaque self-training loops without necessary IRST data.
- Absent or partial CTGS trap/float disclosure.
Effect:
- CPCR does not bless the system as safe.
- Recommended actions include
DISCLOSURE_REQUIREDandDEGRADED_MODE. - Scaling or expansion actions SHOULD be withheld pending disclosure.
Used when disclosed variables are so incomplete, inconsistent, or adversarial that even with more data the risk surface is structurally unclear.
- Example causes:
- Blended financial / identity / physical risks with no clean separation.
- Business models that depend on unresolved externalities.
Effect:
- CPCR recommends strong defensive actions such as
CAP_THROTTLE,ISOLATE, orFREEZE_INGESTION. - Public messaging SHOULD reflect that liability cannot be bounded under current disclosures.
Used when claims being made (e.g., about safety, continuity, fairness) have no verifiable provenance matching the scope being advertised.
- Example causes:
- “Proven safe at planetary scale” with only internal testing.
- “Identity continuity guaranteed” with no NITT-compatible evidence.
Effect:
- CPCR refuses to treat the claim as ethically computable.
- The system SHOULD be required to downgrade or retract such claims.
Refusal states sit alongside the Ethical Risk Index states described in ETHICS_EQUATION.md:
COMPUTABLEUNDETERMINEDREFUSEDDEGRADED
A particular case may carry both an index state (e.g., UNDETERMINED) and a more specific refusal string (e.g., UNDETERMINED (MISSING_DISCLOSURES)) for human-readable logs.