Act

Govern every tool call.

Agents cross boundaries faster than anyone can enumerate them. Every crossing is covered without being configured.

Where you are today

You cannot say what data your agents used or sent last night.

They are calling tools, pulling records and handing context to each other thousands of times an hour, and the vast majority of those crossings remain unchecked.

Most of them are unchecked, and the ones that are checked were checked because someone remembered to configure it.

What changes with NOL8

Every crossing goes through one control.

Inputs are validated before execution and outputs are checked before they feed the next step, per rule, per agent, per role.

Every verdict goes on the record for auditability.

Coverage is not configuration

Data passes through the plane and cannot be bypassed, so coverage is never something anyone has to switch on. That matters more with agents than anywhere else, because an agent adds crossings faster than anyone can enumerate them.

Tool calls

Validated before they execute.

Retrievals

Every record pulled crosses the plane.

Agent to agent

Payloads handed between agents, read as they pass.

The output

Checked before it leaves.

A new tool is covered the moment it is called, not when someone remembers to add it.

Your stack stays as it is

Between the agent and everything it calls.

NOL8 is not a framework. Your orchestrator, your tools and your agents stay exactly as they are; the plane sits in the calls between them.

If NOL8 already filters your corpus at train or checks prompts at inference, agentic adds nothing new to deploy. Same plane, one more place.

Common questions

Every tool call, retrieval, agent-to-agent payload and output crosses NOL8, so coverage stops depending on configuration discipline.

No. The plane sits in the path, not beside it, so there is no route that skips the check.

Every NOL8 verdict is on the record, which sits off the path. The answer is a query, not a reconstruction.

NOL8 covers four of the seven: data and context engineering, deploy and gate, operate and observe, and scale and optimize. We make no claim on the other three. See where it fits →

Uncertainty sucks.

Stop estimating. Your rules, your payloads, your P99.