Open governance framework · v1.3 · Practitioner-led · not an accredited standard, certification, or regulatory requirement · seeking shadow-evaluation partners
Home/Framework/Reference Implementation

Open source · CC BY 4.0

Reference implementation

A working implementation of every control in the specification — so “conformant” means something you can run, not something you can claim.

What ships

ENGINE

Policy engine

Pure Python with zero runtime dependencies. Evaluates each control against a session and event and returns a deterministic verdict.

MIDDLEWARE

TypeScript middleware

Request-path enforcement for Node services, mirroring the Python engine’s verdicts.

ADAPTERS

VAPI & Twilio adapters

Accept native call payloads from either platform and normalize them into the evaluation format — no transcript reformatting required.

AUTH

NHID-Auth v2

Ed25519 agent passports, provider-signed delegation, and offline verification. Details →

SCHEMA

Trace schema

The machine-readable audit envelope every event validates against, published as JSON Schema.

TOOLING

OpenAPI, Postman, PowerShell

An OpenAPI description, a Postman collection, and a PowerShell module for teams whose operations tooling lives there.

Determinism is the point

The engine contains no model calls and no scoring heuristics in the control path. The same session and event produce the same verdict on every machine, every run. That is what makes a conformance claim checkable by someone who does not trust you — including a regulator, an auditor, or a competitor.

It is also what lets the same control logic run in three places without drift: in the test suite, in the simulator, and in production enforcement.

Getting started

1

Clone and run the tests

The repository ships with its full test suite. Run it before you write a line of integration code.

Get the repository →
2

Try the live API

Demo routes require no key. Send a VAPI or Twilio payload and read the verdict.

Open the API explorer →
3

Wire it into your stack

The developer guide covers architecture, the event schema, and the failure-injection harness.

Read the developer guide →

Build on it

Everything here is CC BY 4.0. Fork it, vendor it, or replace it with your own engine and test against the same suite.

NHID-Clinical is a voluntary open framework — not an accredited standard, certification, or regulatory requirement. Everything on this page is published under CC BY 4.0.