What This Is.

This page exists because the work shows up in many places, in many voices, and there is no single artifact that names what they are all pieces of.

So: this is one project. Same author, same framework, same body of ideas. The surfaces look different because they speak to different audiences. The center is the same.

§01the center

The project rests on a single load-bearing claim:

Trust, attention, autonomy, cooperation, and any cognitive system that depends on multiple agents acting reliably together are not properties of the agents. They are properties of the substrate the agents share: the common ground everything runs on.

Where the substrate holds, the integral grows. Where the substrate fails, the agents fail with it. The work is to engineer the substrate.

That claim is being developed in several voices because it touches several domains. The math version is the Trust Force Equation. The clinical version describes what happens to a mind when steady, reliable presence disappears. The infrastructure version is the Kinetic Trust Protocol. The narrative version is the acequia, the centuries-old irrigation commons of New Mexico. The political version asks who controls the ground everyone else must stand on. They are all saying the same thing in different vocabularies.

§02the surfaces

Many surfaces, one center. They group four ways — read, reason, build, explore — so you can scan by intent rather than scroll. Select a surface to expand it; internal links land within the site, external links open the artifact where it lives.

Different doors. Same room.

§03find your path

Choose a curated journey for your interests, with a reading estimate and a clear sequence of pages. If you want help choosing, the optional questionnaire asks about your interests and suggests a starting point. Your answers stay in your browser; the site does not send them to the author.

choose a journey →

§04working on KTP

I found the math, the geometry, whatever it turns out to be, and I started writing, thinking, documenting, and building in public. That is how I met Mike Storm.

Before KTP had a name, Mike stretched the ideas, asked questions I had not thought to ask, and leaned in with a curiosity that finally made it click. The Experience Equation started all of this. Because of Mike, the Context Tensor got its name.

After KTP, Ambient Breach arrived the same way. Mike carried a line from my essay Break the Chain forward, from ambient risk and ambient threat to ambient breach. It reads like crisis mode in a hospital.

Those contributions, and the collaboration along the way, are how KTP became what it is now.

The origin runs deeper than the two of us. My wife, Nayomi, changed how I think, and her three principles are woven into the digital web this framework describes.

KTP’s shape is still being discovered, and it may always be. How it holds inside a Blue Zone draws on culture, history, religion, science, and sociology, all of it.

I have been curious my whole life. I see this work as connecting the dots between details that were shared all along, waiting for someone to notice.

Day to day, I am a Solutions Architect at Splunk, a Cisco Company. Mike is a Cybersecurity Distinguished Engineer at Cisco, on the autonomous threats this framework is built to bound.

The project runs nearly every day. What it has revealed is that treating every interaction as substrate-dependent changes what you notice, in every context where trust is the load-bearing variable. The work is its own argument.

mailto:linkedin

§05what this project is not