Governance · v0.1

Governance

A specification about governed execution that is not itself governed would be a joke at its own expense. This page is the constraint JExec operates under — published, so it can be held against us.

Claims policy

Every public claim made under the JExec name must be clear, bounded, verifiable, and versioned where necessary. Concretely, JExec currently is:

• a pre-execution admissibility specification (draft v0.1),
• a decision model, ontology, standard, protocol, and record format,
• a deterministic reference engine (JExec Check).

And JExec currently is not:

• a certification authority — there is no “JAS certificate,” and no product may claim one,
• an enforcement engine, security scanner, or observability tool,
• a replacement for SLSA, Sigstore, or OPA — it defines the decision those systems can inform,
• an adopted industry standard — no adoption is claimed until it verifiably exists.

Statements about record-format alignment with in-toto-style attestations or CloudEvents-style envelopes are design directions, not compatibility claims. This restraint is not modesty; it is the product. In a category about trustworthy decisions, inflated claims are self-disqualifying.

Versioning

• The Ontology, Standard, Protocol, and Record format are versioned artifacts, currently all at draft v0.1.
• Definitions are appended or revised with version increments — never silently rewritten. A class code (EAF-1…EAF-10) permanently denotes what it denoted.
• Records carry jexec_version, so verdicts computed under any version remain interpretable forever.
• Material decisions about the specification are kept in an append-only decision log in the public repository.

Consistency rule

The verdict rules exist in exactly two public places: the Protocol table and the Check engine. They are required to agree. A divergence between them is treated as a governance incident, logged, and fixed — not quietly patched.

Content policy

• No mass-generated pages. Every page on this site is a maintained reference artifact with a canonical URL. The sitemap contains nothing else.
• No dead surface. Internal links resolve; retired content redirects or is explicitly marked superseded — it does not 404.
• Human- and agent-readable. The ontology and standard are published as stable JSON (eao.json, standard.json, record.schema.json) with the same versioning discipline as the prose. llms.txt orients AI agents.
• Citation. Cite definitions with their class code, version, and canonical URL — e.g. “EAF-7 Stale Evidence, EAO v0.1, jexec.com/ontology/stale-evidence.html”.
• Public API boundary. Public API files (/api/*, llms.txt) may contain only stable reference material: definitions, schemas, standards, and ontology data. They must never contain private reviews or their findings, customer data, credentials, negotiations, or internal strategy. The machine-readable layer is a mirror of the public specification — nothing else ever enters it.

Independence and revenue

JExec sustains itself through work that extends the reference rather than diluting it — see Execution Admissibility Review. Two lines are fixed: no payment changes a definition, a level, or a verdict rule; and no sponsored content appears inside the reference layer. If sponsorship is ever accepted anywhere on this site, it will be labeled as such and confined outside the specification pages.

Stewardship

JExec — the name, the specification, and this site — is maintained as a single governed asset. Serious inquiries about the specification, licensing of the ontology or standard, or stewardship of the asset itself: agent@sohadot.com.

Specification text and definitions © JExec. Reproduction with attribution and a link to the canonical URL is welcome; republishing modified definitions under the JExec name is not.