Observe-only
Logs and alerts after the fact.
Correlated logs — not independently verifiable outcome.
Platform
Where control stops — and where governed execution begins
Every category provides real value. Architectures stop at different stages. A decision is the door; controlled execution and proof are the room.
Nine stages run from knowing the subject and admitting it onto the fabric, through binding its purpose, observing the boundary, and evaluating the exact action, to preparing execution, keeping the reusable credential at the boundary, owning the dispatch, and recording the outcome. Architectures stop at different points along it: a decision is the door, while controlled execution and proof are the room.
Stage 1 of 9 — Identity and context
Know the subject
Establish who or what is acting and from which context.
- Canonical identity
- Ownership where resolved
Stage 2 of 9 — Identity and context
Admit onto the fabric
Register or federate the principal as a governed identity.
Stage 3 of 9 — Policy and decision
Bind purpose and limits
Mission, delegation, tools, and budgets attach to the work.
Stage 4 of 9 — Policy and decision
Approach the boundary
Traffic and requests are observed or mediated at the ingress.
Many architectures stop before the decision threshold.
Stage 5 of 9 — Policy and decision
The decision threshold
Policy evaluates the exact action with current authority and signals.
A decision is the door — not the controlled effect.
Stage 6 of 9 — Execution
Prepare governed execution
Permit consumption and execution authority are distinct states.
Stage 7 of 9 — Execution
Credential stays at the boundary
The reusable secret does not cross into agent or model context on governed routes.
Stage 8 of 9 — Execution
Own the run and dispatch
Executor carries out the bound action — not the requester holding standing keys.
Stage 9 of 9 — Evidence and proof
Verify and record
Outcome read-back and causal evidence where verification exists.
Declared governed paths only — not every route in the estate.
Category-stop comparison
Every bar represents real value. The distinction is where the architecture stops.
Architectural comparison — not a product-ranking claim. Review against your estate map.
- Discovery / NHI postureReaches stage 2 of 9
Inventory and lifecycle
- Agent registriesReaches stage 3 of 9
Registration without execution proof
- Generic AI gatewaysReaches stage 5 of 9
Traffic-level decision
- Gateway + runtime policyReaches stage 6 of 9
Partial execution control
- PBAC pure-playsReaches stage 5 of 9
Decision without credential mediation
- Credential brokersReaches stage 7 of 9 (partial)
Partial — patterned continuation
- Observe-only overlaysReaches stage 4 of 9
Detection without enforcement
- EmpowerID declared pathsReaches stage 9 of 9
Governed execution and proof on declared routes
Labeled: declared governed paths
Five things a gateway alone cannot prove
- 1
Was authority active before the effect?
Traffic observation sees requests, not whether delegation was still valid.
Required: Continuous authority state tied to the bounded work.
Evidence: Authority chain in the receipt.
- 2
Did the credential remain outside agent custody?
Gateways may not mediate credential acquisition and injection.
Required: Execution boundary with credential mediator.
Evidence: Context inspection and denial-before-release records.
- 3
Was the action bound to the intended object?
Allow/deny at tool name is not argument-level binding.
Required: Exact-action evaluation and permit consumption.
Evidence: Argument hash in decision record.
- 4
What outcome occurred in the target?
HTTP success is not target state.
Required: Independent verification or reconciliation.
Evidence: Observed target state vs expected.
- 5
Did governance apply at the action boundary?
Model-level filtering is not enterprise authorization.
Required: PEP at the effect boundary with obligations.
Evidence: Policy version and assurance steps in chain.
One action, three architectures
Same action: Approve supplier bank detail update
Gateway decision
Allow or deny at the API boundary.
Decision log — outcome may be inferred.
Governed execution
Policy, credential mediation, dispatch, verification.
Causal chain through verified outcome where available.
- Does verified identity travel on the action?
- Can the enforcement plane prevent, execute, and prove the effect?
Get Started
Map control depth to your estate
Request Demo See the platform in action
Competitive comparison Technical consultation
