In Development · Early Access Open

ASE Gate — Execution Governance

The gate between machine intent and real-world execution.

ASE Gate is the runtime mode of the Auditome Sovereign Engine — designed to evaluate whether a machine or system action may proceed, before consequences occur, and to return a decision with a traceable, signed record. In development. Early access open.

Request Early AccessRead the Knowledge Article

What ASE Gate Does

Evaluate intent. Return a decision.

Systems submit an intent to ASE Gate. It is designed to evaluate that intent against policy, authority, risk, and execution rules and return a recorded decision with stated reasons before anything runs.

ASE Gate evaluates

  • Policy
  • Risk
  • Tenant identity
  • Execution rules
  • Approval requirements

ASE Gate returns

  • approved

    Action may proceed

  • rejected

    Action is blocked

  • requires_human_review

    Escalated for human approval

Every decision includes

  • trace_id
  • risk score
  • reason(s)
  • audit trail

Why ASE Gate Exists

Before consequences occur.

Most systems

Can tell you what happened. Logs are recorded after execution. Audits run after the fact. Accountability arrives after consequences.

ASE Gate

Helps determine whether an action should have happened before consequences occur. Authorization, accountability, and approval boundaries are designed to be enforced at the execution boundary, not reconstructed afterward.

Authorization

Should this principal be allowed to perform this action?

Accountability

Every decision has an owner, a trace, and a record.

Approval boundaries

Define which actions require human sign-off before execution.

Execution governance

Enforce rules at the point of action, not the point of review.

How It Works

One call. One decision.

Intent
↓
ASE Gate
↓
Decision
↓
Execution

The system submits a structured intent. ASE Gate is designed to evaluate it and return a decision synchronously. Execution only proceeds if the decision is approved.

Planned decision record
{
  "decision": "approved",
  "trace_id": "ase_tr_...",
  "risk_score": 0.3,
  "reasons": [],
  "audit_ref": "aud_..."
}

Every decision will include a trace_id and audit_ref for downstream traceability. This is the planned response shape — ASE Gate is in development.

One engine, two modes

Diagnostic and Gate.

ASE Gate is not a separate product. Diagnostic and Gate are two modes of the Auditome Sovereign Engine — the same engine, applied at two different points.

Diagnostic mode

ASE Foundation Diagnostic

Available now

ASE inspects an AI-built or AI-assisted codebase read-only and reports what it can and cannot prove.

Explore the Foundation Diagnostic →

Gate mode

ASE Gate

In development

ASE sits in the execution path, evaluates intent against policy and authority, and returns approved, rejected, or requires_human_review with a signed decision record.

The diagnostic shows where your system cannot prove itself. The gate is designed to enforce proof at the point of action.

In Development

ASE Gate is being built.

The architecture is defined. The three decision states — approved, rejected, requires_human_review — are the designed interface. The policy evaluation model, trace record format, and audit persistence layer are specified.

ASE Gate does not have a live endpoint yet. If you need to evaluate AI actions against policy before they execute, register your interest and we will contact you when access is available.

Register Interest