5D resources

Learn the boundary. Inspect the evidence.

Guides explain the implementation questions. Evidence records show what 5D supports today, what the examples demonstrate, and where the limits remain.

Implementation overview

One policy path for throughput, control, and shared evidence.

For high-volume agent applications, keep declared actions on an inspectable policy path and route only the cases your policy selects for optional semantic evidence or review.

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.

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.

  1. Policy ownerDefines rules and review thresholds
  2. EngineerIntegrates the action boundary
  3. SecurityChallenges threats and bypass paths
  4. ReviewerRecords the required human decision
  5. Evidence ownerMaintains replayable records

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.

CISO lighthouse

The AI agent governance lifecycle.

A source-linked control map across EU, UK, Singapore, NIST, ISO, and OWASP, with 5D contribution and organisational responsibility kept side by side.

Guides

Three implementation paths.

Each guide is matched to the tested release and reviewed against the available evidence.

Evidence

7 topics, stated with their limits.

Evidence pages separate shipped behavior, worked examples, and framework mappings. They do not establish compliance.

Author’s Articles

Longer arguments on the professional site.

These are curated links only. The article bodies remain canonical on langoni.me.

Runtime governance

Runtime Is the Moment of Consequence in AI

Why governance becomes real when an AI agent is about to act, and what historical safety failures teach about that boundary.

Read on langoni.me ↗
Execution boundary

When AI Governance Reaches the Execution Boundary

How governance intent becomes an action-time decision and a record that can be inspected later.

Read on langoni.me ↗
Authority

The Model Can Be Probabilistic. The Authority Boundary Should Not Be.

A technical argument for combining deterministic control, typed judgments, and fail-closed review in high-risk agent paths.

Read on langoni.me ↗
Testing

How Do You Test a Control That Can Never Fail?

A practical guide to mutation, path evidence, and an explicit unevaluable result for safety and policy controls.

Read on langoni.me ↗
Infrastructure

The Infrastructure Consequential AI Agents Need

A wider view of bounded authority, evidence, and recourse for agents that can affect money, data, rights, or services.

Read on langoni.me ↗
Human review

AI Agent Approval Fatigue Is Real

Why asking for approval on every harmless action weakens the human-control loop, and what a policy layer changes.

Read on langoni.me ↗
Open infrastructure

How Open Source Saved the Internet

How open protocols, shared software, and viable ecosystems kept the internet contestable, and why AI faces a harder version of that test.

Read on langoni.me ↗