the horizon where assurance and enforcement converge

A network that verifies itself.

Business intent becomes network intent. Network intent compiles into policy. The fabric enforces it and counts what crossed. The engine holds what ran against what was declared, and the evidence feeds the next change. Close that loop and the network stops being something you audit and becomes something that keeps proving itself.

This is not a new engine. It is what assurance and verified enforcement become when they run on the same estate long enough to trust each other — and it is the reason the two products are shaped the way they are.

SRv6-native the horizon — said out loud

0100 the loop

Five verbs. Each one is a product you can stop at.

The journey is linear on purpose; the buying is not. Most estates live at the second verb for years. Some never leave it. The last verb exists so that the first four are designed to get there.

01

Discover

Build the network truth: what is declared, configured and observed, on the estate as it is.

core

02

Verify

Keep that truth aligned with intent, continuously. Drift becomes a verdict, not an anecdote.

core

03

Enforce

Turn verified intents into segments that count what crossed them.

SRv6

04

Control

Prove the path, not just the reach — chain, geography, jurisdiction.

SRv6

05

Automate

Intent to evidence with no hand in between — for the change classes that have earned it.

horizon

core 01 and 02 are assurance SRv6 03 and 04 are verified enforcement 05 is this page

0200 earned automation

Write access is unlocked by your own history. One change class at a time.

The failure mode of intent-driven networking is a system that confidently does the wrong thing at scale. So automation here is not a mode you switch on. It is a privilege each class of change earns, and can lose.

A class of change automates after N human-applied instances verified clean. — the customer's own evidence history is the trust currency. Not a vendor's confidence score, not a model's probability: a count of times this exact kind of change was compiled, applied by a person, and proven to have landed as intended.
Sensitive classes keep a person in the loop permanently. — some changes should never be a machine's to make alone, and saying which ones is part of declaring the intent. The named human is a feature of the design, not a stage it grows out of.
A failed post-change verification proposes its own rollback. — the engine already proves whether a change landed as intended. When it did not, the rollback is compiled and queued the same way any other change is — for a person, or for the class that has earned the right to apply it.
Only declared intent may widen. That rule never relaxes. — the discipline that makes assurance honest is the seed of the safety argument here: observed traffic is evidence, never authority; an unowned flow cannot be widened; a gate that cannot fail is theater. Automation inherits all of it.

0300 said out loud

This is a horizon. We would rather say so than sell it.

What exists today

The deterministic engine, the declared lane with named approvers, the gates that are shown going red, the replayable evidence — every piece the loop is built from is the piece assurance already runs on. Nothing here is a new engine.

What does not

The closed loop itself. Design begins when an estate is concretely targeting enforcement; until then it is not roadmapped, and there is no date on this page. A company selling verification cannot be the one place it is not applied.

Why it is here at all

Because it explains the shape of everything else: why the audit produces intent-as-evidence, why enforcement is earned, why no write credential is ever asked for early. The horizon is the design constraint, not the sales pitch.

Start where it is provable today. The loop is what the first two weeks are quietly building toward.

e000 End.DT6 deliver

Start with the audit.

30–60 minutes, read-only, on the estate you run today. Everything on this page begins with the same first byte.

See it on your estate — read-only