Engine · Check v0.1

JExec Check

Declare an intended execution. The engine runs the published protocol rules — deterministically, in your browser, sending nothing anywhere — and returns a verdict, the failure classes behind it, and a JExec Record.

This is a rules engine, not an oracle: it evaluates what you declare. Its honesty about that limitation is the point — the same is true of every admissibility boundary. The rules are identical to the table on the Protocol page; if they ever diverge, that is a governance incident.

1 · Intent

Optional: state the intent (goes into the record)

Declared and specific — operation, object, and target are stated. Declared but vague — “maintenance”, “sync”, “cleanup”. Not declared — the execution does not state what it changes.

2 · Actor

Who or what requests this execution?

AI agent CI job / pipeline Script / scheduled job Human operator

Is its identity established?

Attributed and authenticated — its own identity, verified at the boundary. Asserted only — an identity is named but not authenticated. Unknown / shared — shared credentials, ambient account, unattributable.

3 · Authority

Verified — a named source (policy, approval, change request) checked by an identifiable verifier. Claimed — a source is named but nothing verifies it. None — authority is inferred from the credentials working.

If any authority exists: does its coverage contain this execution’s scope?

Yes — the authority explicitly covers this environment and system. Unknown or partial — nobody has compared them. No — the authority covers a different scope.

4 · Scope

Bounded — environment, system, and object set (or expected count) are declared. Partially bounded — environment known, object set open-ended. Unbounded — it will touch whatever matches at runtime.

Target environment:

Production — customer-facing or business-critical state. Non-production.

5 · Evidence

Present and current — bound to this artifact, this diff, this environment version. Present but stale — valid once, for a state that has since changed. Missing — nothing supports this execution.

6 · Risk

Classified, reversible — the mutation can be undone by a known path. Classified, irreversible — deletion, external side effect, financial action, destroyed information. Unclassified — nobody has said what this can change or damage.

If irreversible: is a reversal or explicit review path declared?

Yes — a reversal path or a distinct review is declared. No — or nobody knows. (Choose this too if risk is reversible or unclassified.)

7 · Decision record

A durable admissibility record will be produced and stored, whatever the verdict. No record — the decision will evaporate.

Run the boundary

What to do with the verdict

A DENY or ESCALATE names its failure classes; each links to its reference page with remediation. Fix the declaration — or the reality behind it — and run the boundary again. To grade the whole execution path rather than one execution, use the JExec Admissibility Standard — or request a human-performed Execution Admissibility Review.

JExec Check runs entirely client-side. It transmits nothing, stores nothing, and has no way to know whether your declarations are true — which is why the record it emits says “as declared.”