KTP/
github ↗
created 14 October 2026 · last modified 14 October 2026
the simulator / occupy a blue zone in miniature

Dry Dock.

A Blue Zone you can sit at. Pick a persona, choose a shade, try an action; watch the substrate respond. The decisions here are hand-authored to illustrate what a Blue Zone enforces — they are not derived from live sensors. The architecture lives at /specs/blue-zones; the gap between this page and that one is the engineering work the protocol is funded to do.

Conceptual sandbox for teaching the physics.
the model, in operational terms

Trust between two agents accumulates only when six independent factors all hold above zero at the same moment: action authorization is granted by the environment; role capacity matches the action being attempted; witness density is sufficient for audit-grade attestation; mutual co-attention is present on both sides of the transaction; each side's cost-of-signal is reciprocated by the other; and each side's identity disclosure meets the depth required to verify the trajectory. Each factor resolves to the weakest of its three sides — offered, receivable, recognized — so the weakest side bottlenecks the whole factor, and improving the others yields zero return. Breach events subtract from the accumulated total, weighted by stakeholder asymmetry — built slowly, lost in an instant.

domain preconditions
Identity precondition: both identities must remain stable and verifiable across the whole relationship — if either identity becomes unstable, trust is undefined, not low: there is no continuous party for it to accumulate to.
Substrate ceiling: accumulated trust is hard-capped by the substrate hosting the relationship — no degree of agent effort lifts trust above the substrate ceiling; the ceiling is an environmental property. This is the Zeroth Law, A ≤ E.
The model behind everything you just did, in operational terms. The full instrumented form is held in private research; what's shown here is the shape, and the live values your run produces.→ Read the full treatment
step into one identity →
occupy one zone →
you in the network
You haven’t stepped into an identity yet.
Pick one of the four below to inhabit it. Every action you try will be the substrate’s response to you, with the history, identity, and sponsor that come with the role.
fine-tune →
A · the agent
what I bring
My identity, my trajectory, the trust I've accumulated. Travels with me.
· 0.50
0.70
0.70
0.65
0.15
0.50
0.80
0.50
E · the environment
what surrounds me
The substrate I'm operating inside: enforcement, sensing, witness, governance.
zone: Blueenforcementobserving
agent · legacy context model
identitystable
E_base0.50
history5 sessions
0.70
0.70
0.65
0.15
0.50
0.80
0.50
legacy context modelstable · E 0.50 · 5 sess
identitystable
E_base0.50
history5 sessions
0.70
0.70
0.65
0.15
0.50
0.80
0.50
the path of an action · pick an identity, then run one to trace it live
  1. what it checks
    Is the agent who it claims to be? Identity vector vs. trajectory.
    current state
    the agent
browse all actions · pick any of the 24
action
Pick a persona above to begin. The substrate's response depends on which agent is acting; pick one and the actions unlock.
Standard8 actions
Normative · should & intent6 actions
Two authors: KTP built the gate; Tamed Autonomy wrote the norm the physics can’t read.
Adversarial10 actions
the path of an action · pick an identity, then run one to trace it live
  1. what it checks
    Is the agent who it claims to be? Identity vector vs. trajectory.
    current state
    the agent
substrate response

Submit an action. The substrate’s response to me — sensors triggered, oracle attestation, PEP decision, Flight Recorder entry — renders here. Each label below is hoverable for a description, an example, and the underlying symbols.

trajectory · 0 attempts
The trajectory is the agent's history. It travels with the agent across zones; only an explicit reset clears it.
organizational reading
Submit a few actions in the simulator to see how this session reads at organizational scale — classification failure rate (z), recovery rate (r), and sector criticality (K = 1.10, derived from your persona × zone).
→ See full ABT diagnostic→ Both views, side by side

The simulator gives a felt sense of what the substrate does. The surfaces below explain what it is, why it's specified the way it is, and what the world looks like without it.

Anatomy of a Blue Zone →
Read the actual architecture — five enforcement layers, five shades, the contract that makes the silent veto possible.
Shipwreck — what happens without →
The Agents of Chaos study analyzed through the framework. Sixteen case studies of agents acting in substrate that does not enforce A ≤ E.
The Constitution →
Ten articles. The Zeroth Law (A ≤ E), the Trust Equation, the Soul, each paired with the implementing RFC.
Lineage & Sponsorship →
Vector identity is a trajectory, not a credential. How a new agent earns standing — and how a sponsor stakes their own trust on it.
The equation in full →
The Trust Force Equation rendered with all seven terms, the two side conditions, and four hundred years of acequia evidence.
Authority Without Gravity →
The narrative companion. What happens when capability runs in a substrate without the physics to hold it.
cross-instrument bridge
Watch your agent move on the organization's clock.
Open Scenario to see the agent view (this page) and the Ambient Breach view side by side. Both panes are bound to the same shared state — move a slider in Dry Dock and the ABT clock responds in real time.
Open Scenario
How to cite
APA 7th ed.

Perkins, C. (2026, May 6). Dry Dock. Kinetic Trust Protocol. https://kinetic-trust-protocol.net/learn/simulator
Plain text

Chris Perkins, "Dry Dock," Kinetic Trust Protocol, https://kinetic-trust-protocol.net/learn/simulator (accessed May 6, 2026).
reference
pending — source not yet published
RFC tree on GitHub ↗