External controlled negotiation protocol (cnp) for automated and AI-driven actions. Not another scanner. A scanner detects after the fact. This boundary decides whether execution may continue.
This repository is the public proof and evaluation surface for an external controlled negotiation protocol (cnp). It is meant to make one point clear: the object here is not a post-hoc detection tool and not a generic security scanner. The object is a separate execution decision surface above workflow-local logic.
This public surface is intentionally paired with the separate GitHub Action surface:
cnp-boundary= proof / evaluation surfacecnp-action= install / Action surface
The commercial transition remains Hosted Authority. Hosted Authority is the separate written commercial path for teams that want a real execution decision layer above workflow execution.
The inquiry path remains singular and controlled. If a team wants real use rather than only proof or evaluation, the canonical next step is the Hosted Authority inquiry path.
A scanner reports. An cnp boundary decides whether execution is allowed to continue. That distinction is the core interpretation key for this repository.
The intended route remains:
- understand the proof / evaluation surface;
- understand the separate Action surface;
- move to the Hosted Authority inquiry path if the team needs real use.
- Action surface:
cnp-action - Hosted Authority path:
HOSTED_AUTHORITY.md - Support path:
SUPPORT.md - License path:
LICENSE
This repository presents the proof surface and the route into a separate written commercial path. It does not describe Hosted Authority as a public live service.
This is the only canonical inquiry entry for Hosted Authority access. GitHub is not checkout.
Pre-run policy is necessary. External admission is the stronger boundary.
Platform-native controls improve the executor. External admission separates execution from authority.
If execution can proceed without an external allow decision, the system has policy, but not external admission authority.
Surrogate Boundary Test: Can execution proceed without an external allow decision?
No Admission = No Execution.
Learn more: