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

TrustLayer · Module 02

Trust Gateway

Runtime enforcement. Controls that only run in a test suite describe intentions; controls in the request path describe behavior.

The verification sequence

Every step is a precondition for the next. A failure at any stage stops the call from reaching the healthcare system — and produces an audit event either way.

TrustLayer runs the same deterministic controls as the open framework — this module adds operations around them, not different rules.

  1. AI AgentAn automated caller initiates contact on behalf of a claimed organization.
  2. 1Identity verificationIs this agent registered, and does its presented credential verify? An unregistered or unverifiable agent goes no further.
  3. 2AuthorizationWas this agent delegated authority by the organization it names — and is that delegation still valid, not expired or revoked?
  4. 3Disclosure checkIDG-01 and DBC-01: did the agent disclose itself as automated before any operational exchange, without deceptive human-presence cues?
  5. 4Scope enforcementPDX-01: is this specific request inside the agent’s delegated scope? An eligibility agent does not get to pursue a claims appeal.
  6. 5Audit eventATR-01: a complete, replayable envelope is written for the decision — including decisions to block.
  7. Healthcare systemOnly requests that cleared every preceding step reach the payer or provider system.

Design commitments

Deterministic in the control path

No model calls decide whether a request passes. Same inputs, same verdict — which is what makes a gateway decision defensible after the fact.

Blocks are evidence too

A blocked request produces the same quality of audit envelope as an allowed one. Silent drops are how incidents become unreconstructable.

Fail closed on the data path

When authorization cannot be established, protected data does not move. Ambiguity resolves toward not disclosing.

Same controls as the open engine

The gateway does not introduce private rules. If the open reference engine would fail a call, so does the gateway.

Development status: TrustLayer is being built with design partners and is not yet generally available. Screens and outputs on this page are illustrative, not live product data.

Related

What feeds the gateway, and what it produces.

TrustLayer by NHID-Clinical is in active development. It is not an accredited standard, a certification, or a regulatory compliance guarantee. The open framework it enforces remains free under CC BY 4.0 and is never gated behind a plan.