What it is
CNOL is the runtime gate that decides whether an action may cross into reality under explicit constraints.
CNOL / Extended Systems
Compliance-Native Operating Layer
Execution gating and provable non-execution.
CNOL is the runtime gate that decides whether an action may cross into reality under explicit constraints.
What problem it solves
Execution systems optimize throughput and policy flexibility. Under ambiguity or jurisdictional conflict, that bias leads to unauthorized action.
What it does
- Permits or refuses execution against explicit authority, policy, jurisdiction, time, and system-state constraints.
- Records refusal and execution as first-class evidence through dedicated ledgers.
- Fails closed and prefers outage over unauthorized action.
What it does not do
- It does not determine truth, justify decisions, explain refusals, or preserve custody itself.
- It does not negotiate exceptions or accept emergency framing as a bypass.
- It is not a generic policy engine that optimizes flow.
Who it is for
- Organizations that cannot absorb a single unauthorized action.
- Environments under multiple jurisdictions, sanctions pressure, or high-risk automation review.
Where it fits
CNOL sits downstream of the Truth Stack and provenance systems with zero upstream influence. It is intentionally killable without contaminating custody.
Typical deployment context
Used where action permission itself must remain explicit, bounded, and provable.
Primary source docs
- What CNOL iscnol/docs/01_what_is_cnol.md
- Architecturecnol/docs/10_architecture.md