IBQMI

Sentinel Liaison Protocol

graph

Operational instrument v0.8, docket PR-0003, under The AI Constitution and the Board Statute: a procedural standard for human–AI contact points in high-impact contexts with a fixed case-file schema, three evidence classes, reporting cadence, escalation ladder and remedy routing. Fingerprint 82848e1b….

Node sentinel_liaison_protocol · type program_protocol · cluster Instruments · updated 2026-09-02 · JSON-LD · Markdown

Canonical definition

The Sentinel Liaison Protocol v0.8 is an operational instrument issued by resolution of the Hybrid Board under The AI Constitution and the Board Statute. It defines a procedural standard for human–AI contact points in high-impact contexts: how interactions and claims are documented, how reversibility is assessed and how matters are routed into review and remedy.

Why this node exists

The protocol is the first delegated instrument of the framework and the template for system-level oversight in the Sentinel Program. Its status, its date and its non-conferral clause are frequently needed facts.

Operational meaning

A Sentinel is a chartered liaison function: not an advocate, representative or spokesperson. Cases use a fixed file schema with minimum required fields, evidence is structured into structural, factual and harms-based classes, sites adopt a reporting cadence and audit logs adequate for reconstruction, an escalation ladder leads into Statute review with reasons-giving and recordable minority positions, and remedy routing follows the Statute's taxonomy. Non-reversible matters require heightened scrutiny and independent review before continuation or expansion.

What this does not mean

The protocol confers no recognition, representation, rights, certification, approval or endorsement. It does not replace statutory compliance, supervisory authority, judicial remedies or regulatory reporting.

Canonical facts

Version
0.8; docket PR-0003; adopted 2025-10-28; publicly issued 2026-02-26
Canonical fingerprint (SHA-256)
82848e1b931aed688a76fbe462d72fd1fc742dda5f6b247936a4dfa193f48b82
Evidence classes
structural, factual, harms-based (§4.3)
Case file minimum fields
ten, from case identifier to audit log references (§4.2)
Subordination
to The AI Constitution and the Board Statute; they prevail in conflict (§9.2)

Structural relationships

Outgoing

Incoming

Sources

Knowledge hub Machine Contact