Technology — Enforcement · HOT
HOT
T
T · The Technology dimension
Technology · Enforcement

The platform has to
carry it.

An agent is only safe to admit into a business if the platform beneath it can enforce what it is allowed to do. Agent-ready is not one thing you switch on — it is a stack, and nothing stands above the layer you skipped.

ENFORCED AT MACHINE SPEED agent actions proposes THE GATE identity on every action logged & immutable integrity at write permitted ✕ blocked {{ packetLabel }} {{ verdict }}
Permitted
{{ permitted }}
Blocked
{{ blocked }}
Written to record
{{ permitted }}
The platform is the floor: identity on every action, a record of every change, integrity at the point of writing — so the organization's permit line is real rather than aspirational.
01 · Problem 02 · Shift 03 · The core 04 · How it holds 05 · Handoff
01 · The problem

It worked in the demo because nothing was at stake.

This is the dimension everyone overfunds and least understands: buy the model, assume the platform will hold, then discover at machine speed that it does not. A demo has no identity to attach, no record to keep, no write to protect — so it proves nothing about production.

The distance between an experiment and a production system is measured in real consequence. Money spent on capability with no containment buys exactly that: capability with no containment.

02 · The shift

Governance moves from the edge to the foundation.

In the software era, control was something you added at the perimeter: a review, an approval screen, an audit after the fact. An agent operating at machine speed makes after-the-fact worthless. What the previous era bolted on, the platform now has to hold natively — identity, permit, record, integrity, at the point of the write.

Can your systems actually carry an agent — or only demo one?

03 · The core

Five layers. Nothing stands above the one you skipped.

Agent-ready is a stack, opened in order. The permit line is enforced inside it — which is why the organization's decision about authority only becomes real at layer four.

Pull a layer out · watch what stops holding

the permit line is enforced here
{{ stackNote }}
04 · How it holds

The floor, not the centerpiece.

Built right, technology is invisible when it works and catastrophic when it does not. The goal is not the most advanced platform. It is one trustworthy enough that the organization can safely widen the permit as judgment earns it.

The unit
One action, fully attributed

Not the system, not the session — the individual action, with an identity attached and a record that cannot be edited after the fact.

The order
Enforcement before execution

The layer that makes everything above it safe belongs in the foundation. Reach the core, do not rebuild it — and never open execution first.

The test
Prove it, then stop it

Can you show exactly what an agent did, and can you stop what it should not do — every time, at the speed it operates? Two answers, both required.

The line HOT holds
Requirement, not stack

HOT names what each layer must do. Which platform, protocol, or vendor satisfies it — and what that means on a particular estate — is a practice's work.

This dimension, pointed at you
Which layer are you missing?

The scan reads each dimension separately and creates a score for each one.

Run the HOT scan → ~4 minutes · No email
Back to the first dimension · three forces
The people have to change first.
H