Protocol Demo v4.1.1 · Live local-LLM governance
Connecting to LM Studio…
OpenAI-compatible · HMAC-signed · Tamper-evident · CRP-* headers

See CRP v4.1 govern every inference call

This demo drives a local model in LM Studio through the Context Relay Protocol v4.1 runtime. Watch the canonical CRP-* header namespace, signed session tokens, window-level HMAC chain, CKF memory, DPE risk scoring, safety budget, and compliance classification appear in real time.

Governed dispatch

Send a prompt. CRP returns a governed response plus every governance signal.

Try a template:
Risk
Quality tier
Grounding
Fabrications
Saturation
Safety budget
Tokens

Context Knowledge Fabric

Facts extracted from model answers are stored, recalled, and cited across windows.

0
Total facts
0
This window
0
Recalled
No facts yet. Start a conversation in the Dispatch tab.

Continuation DAG

CRP windows form a DAG: LINEAR, FAN_OUT, FAN_IN, and BRANCH. Each window carries a continuation ID and a window HMAC.

No windows yet.

Tamper-evident audit chain

Every window has a HMAC chained from its parent. Tamper with one window and the chain breaks.

No events yet.

CRP-* header namespace

Every governed response carries the canonical CRP v4.1 header set.

Policy enforcement

Declare a safety policy and watch CRP halt generation when risk crosses the threshold.

Compliance classification

CRP classifies each response against EU AI Act, GDPR PII, NIST, and ISO 42001 controls.

Multi-agent safety

CRP headers travel with A2A/MCP agent messages. The safety budget acts as a circuit breaker across hops.

Safety budget
Circuit state
Budget health
Loop depth
Tool calls
Windows

Active AI safety

CRP runs Layer 1 validation, Layer 2 injection/PII scanning, DPE risk scoring, policy enforcement, safety budget, and HMAC audit chains. These checks are active: they happen on every request, are surfaced in CRP-* headers, and are recorded in the tamper-evident audit log.

No dispatch yet.
No dispatch yet.

Unlike black-box guardrails, CRP publishes its full safety surface: capabilities, defaults, coverage rules, and explicit out-of-scope items.

Click the button to load the surface map.