The docs.

Operational entry into the Secure Agentic Intent-to-Runtime Protocol. Separates intent, authority, and execution. Establishes that execution must consume already-verified authority, not infer it.

The governance model in one document. Authority binding, invariant evaluation, ledger evidence, and the boundary between development-time and gate-time claims.

The four-phase protocol traced end to end. Negotiated transaction authority (NTA), ACK envelope agreement, admission handshake, and execution under enforce(). Each phase has a sub-anchor and links to its underlying specification.

Terminal HALT semantics: codes, namespace, and routing. The non-optional state-transition stop. Combines code catalog with namespace structure.

The execution-phase engine that consumes admitted events, evaluates invariants, and emits PASS or HALT. The runtime equivalent of enforce(event).

Unified contracts and interface architecture across the meetLab surfaces. What each component must accept, what it must emit, and how authority flows through the boundary.

Formatting specification and schema for the v1 corpus. How sessions, turns, and labels are represented; what the canonical SQLite shape looks like.

The single hash semantic across ledger, capsules, and audit trail. Cited by verify_shcl_chain.py and test_hash_unification.py. The basis for replayable evidence.

SAIRP-level operations for the full meetLab platform. Build entry, artifact promotion, runtime state, and the day-to-day operator surface.

Operating the editorial pipeline. Six stages — segment, canonicalize, compress, bind, evaluate, seal — wired into a deterministic chain that emits the Final Execution Envelope. Includes the HALT Matrix, the cryptographic amnesia boundary, the 22-code error namespace, and the recovery decision matrix.

The deterministic ingestion and analytics pipeline. Four phases, seventeen ordered tools, and the unified integration/ layer that wraps GAUNTLET with cross-domain contract checks. Includes the DB-vs-filesystem boundary, the DB safety contract, and a failure-triage flow.

Two Tier-2 statutory protocols govern off-surface execution. ATL-001 binds tool-call events to authority; MRP-001 binds model relay and MCP messages to artifact-anchored payloads. Both gate on active_envelope_hash and fail closed.