JExec

Reference · EAO v0.1 (draft)

Execution Admissibility Ontology

There are only so many ways an intended execution can fail to be admissible before it mutates state. The EAO names them.

Most execution incidents are described afterward in the vocabulary of their symptoms: the outage, the data loss, the wrong email. The EAO classifies them by the admissibility failure that let them run. Ten classes, mapped to the seven questions of the JExec model. Each class page defines the failure, shows how it appears across agents, CI, and human operators, explains why it defeats admissibility, and states its default consequence under the JExec Protocol.

An execution that exhibits none of these ten classes is admissible. That is the definition, not a slogan.

The ten classes

How the classes map to the model

Using the ontology

Run an intended execution through JExec Check to detect these classes deterministically and produce a JExec Record. Measure a system’s overall posture against the JExec Admissibility Standard. The ontology is also published as machine-readable JSON at /api/eao.json for agents and tooling.

The EAO is versioned under the JExec governance policy. Classes are appended, never silently redefined.