The governed boundary between a human voice and an AI system.

Every query is distilled, evaluated, and attested before it crosses the boundary. Every response is attested before it returns. Nothing moves without a Chronicle record. The audit chain is not a receipt. It is the gate.


The problem with raw principal-to-AI interaction.

Most AI interfaces are direct: human input arrives at a frontier model, a response comes back. No evaluation of what was asked. No governed record of what was returned. No attestation that the boundary crossing was authorized.

In a consumer context, this is acceptable. In a regulated enterprise, a defense contractor, a healthcare system, or any environment where the humans at the top are legally accountable for what the AI did — it is not.

The audit standard is not obsolete. It is unusable at agent execution speeds without a governed interaction protocol.

Elenchus is that protocol. Every interaction between a human principal and a governed execution substrate passes through two evaluation gates before reaching any external AI API. Every response passes through an attestation gate before returning to the principal. Every cycle — success or failure — produces an immutable Chandra Chronicle record.

Voice is the reference transport. The protocol is transport-agnostic.


Five stages. One external exposure. No unattested crossings.

Every Elenchus Unit (EU) — one complete governed interaction cycle — traverses this pipeline in order. No stage may be skipped.

1
Ingestion
Raw principal input received by the Substrate. Transport layer stripped. Normalized input passed forward.
2
Distillation Gate 1
A governed local model evaluates the query for intent, scope, and safety. No query reaches an external API without passing this gate. The model's identity is attested by hash in every Chronicle record.
3
Graph Evaluation Gate 2
AllegroGraph applies clarity and safety filtering to the distilled output. Boundary compliance and semantic coherence evaluated before any external dispatch is permitted.
4
External Dispatch
The single sanctioned external exposure. Query forwarded to the frontier AI API. This is the only point at which the governed boundary is crossed. All other computation is Substrate-local.
5
Response Attestation Attest
The frontier API response is evaluated by the Substrate. A Chandra CU is written. The EU closes. Only then is the attested response delivered to the principal.
A response that cannot be attested is suppressed. The EU closes with a failure record. The principal receives a governed error response.

The EU. One cycle. One record. Always closed.

The Elenchus Unit is the atomic primitive of the protocol — one complete governed interaction cycle. An EU opens on principal input and closes when a Chandra CU is written. An EU that does not produce a CU has not closed. There is no other terminal state.

Open
EU Created
EU identifier assigned on principal input. Timestamp recorded. Pipeline begins.
Processing
Pipeline Traversal
EU carries state through all five stages under a single identifier. No stage output bypasses the next.
Closed — Success
Attested Response
All five stages completed. Response delivered. Chandra CU written. EU identifier retired.
Closed — Failure
Failure Record
Any stage failure closes the EU immediately. Failure CU written with stage-of-failure recorded. Principal receives a governed error response.
Design principle
Fail Fast. Attest Everything.
Failed EU attempts are not a deficiency — they are an audit asset. A regulated environment benefits from knowing what queries failed, at which stage, and how many times. Elenchus produces this record by construction. The principal rephrases and opens a new EU. Each attempt is independently attested.

Elenchus as the GABA attestation mechanism for governed AI dialog.

Every EU closure event produces a Chandra Chronicle Unit. The CU carries the EU identifier, pipeline stage-of-failure (if any), model hash reference, session identifier, transport binding, and the hash of the preceding CU in the chain. The Chronicle is the authoritative record of all principal interactions.

A conforming Elenchus implementation must produce a GABA Standard Governed AI Boundary Attestation Report (ABRAR). The ABRAR must reference a Chandra CU as its mandatory attestation anchor. An ABRAR without a CU reference is a document. An ABRAR with a CU reference is an attestation. Elenchus requires attestation.

Read the specification Chandra Protocol ↗

Open protocol. Governed standard.

Elenchus is MIT licensed. The specification is the contribution. Reference implementation is provided by Aegis Genera in Allegro Common Lisp on a Yocto build substrate.

General Reasoning, Inc. maintains the Distilled Model governance criteria, the Elenchus NLQ Evaluation Suite, and the evaluated model registry published at this site. Governance follows the benevolent dictator model — merge authority is not shared. A governed protocol with open merge authority on its evaluation suite is a protocol that can be poisoned through contribution.

NIST standardization of the Distilled Model governance criteria is in progress.

General Reasoning, Inc. · Birmingham, Alabama · MIT License · 2026
Enterprise inquiries: inquiries@genreason.com