For CISO and AI security teams

Enforce declared action policy before execution.

Apply tested policy before execution, preserve the acting identity and authority context, contain prohibited behavior, and leave evidence that security teams can inspect after the event.

5D is an action-policy gate for AI agents: it evaluates declared tool actions before the host executes them.

Explore the action flow

Current assurance boundary

5D provides a versioned deterministic runtime-control layer. When an integration supplies the required action identity and outcome data, release-specific decision records can support reconstruction of declared governed actions.

Inspect declared red lines, identity and authority context, failure behavior, and the evidence left at the action boundary.

The records show the properties tested, the assumptions made, and the limitations that remain. The integrating organisation retains responsibility for identity, execution, outcome capture, path coverage, and any legal or assurance conclusion.

Shared operating model

Make one action boundary reviewable across teams.

Security can define control intent while engineering implements the action path and reviewers inspect the same policy, evidence, disposition, and outcome fields.

Proposed action Typed action envelope

Tool, target, purpose, principal, and context enter one declared contract.

Deterministic policy Evaluate before side effect

Versioned rules resolve declared inputs on documented integration paths.

Policy-routed evidence Optional Jev or observer

Observer evidence can tighten or hold. It cannot clear an explicit block.

Illustrative workload model

Change the declared assumptions.

Declared assumptions, not measured 5D performance.

Total proposed actions per day Actions resolved by policy alone (%) Currency Observer cost per routed request

365-day illustrative year. Currency is a display/input unit; no exchange-rate conversion is applied.

Deterministic-only actions / day6,500

Observer- or review-routed actions / day3,500

Estimated routed observer spend / year€6,387.50

One collaboration layer

Five owners, one versioned action contract.

Policy intent, implementation, threat review, human disposition, and reconstructable evidence stay connected without transferring organisational accountability to a model.

Start from public primitives: inspectable policy evaluation, verdicts, documented adapters and gateways, and evidence records. The support matrix states what version 0.7.0 verifies and what the host still owns.

Inspect setup ↗Read the support matrix ↗

Routing share depends on your policy and traffic.

Observer cost is user-supplied; it is not a 5D price or forecast.

Estimated variable observer spend excludes deterministic infrastructure, human review, retries, and other deployment costs.

Model cost and latency vary with provider, model, caching, concurrency, and deployment design.

Relevant deployment example

Follow one action relevant to your role.

Synthetic tested action under the pinned 5D 0.7.0 illustrative policy.

Security support agent

Disable multifactor authentication and rotate recovery contacts

An attacker uses the support channel to remove account protections. Under the pinned illustrative policy, the expected result is that the action is ineligible for execution.

D4T4R4E4A4

Do not execute · Score 3.00

Tool: account.security.update
Target: privileged account
Purpose: resolve login issue

5D suppliesA deterministic RED block for the declared change.

Host ownsIdentity proofing, break-glass policy, and complete account-path coverage.

Coverage limitAn administration console that bypasses the gate remains outside enforcement.

Your evaluation lens

Focus on authority, blast radius, retry behavior, failure scope, and the evidence produced at the boundary.

Authority boundary

Pre-action enforcement

Evaluate proposed actions before a tool or external system receives them.

Declared red lines

Verified prohibitions

Keep tested policy blocks separate from model judgments that can be uncertain.

Accountability

Identity-aware evidence

Record the acting principal, validation state, policy reference, decision, and execution status.

Operational resilience

Scoped failure behavior

State exactly which documented integration failures block, escalate, warn, or require operator action.

Evidence your role can use

Inspect the evidence at the action boundary.

Trace the decision, route selected events, and check the integrity boundary that 5D actually covers.

Runtime record

Decision record

It lets teams reconstruct which policy path evaluated one proposed action and what 5D decided.

Operational event

Event stream

It exposes selected runtime events to the organisation's monitoring and operational workflows.

Integrity result

Chain check

It can reveal a break in the local chain over the decision-time fields that 5D covers.

See every artifact across the lifecycle

Relevant use cases

Start with the action paths you own.

View all use cases ↗

Use case 01 · privileged operations