The Common Names.
Every domain has always had a name for the thing underneath the thing. Farmers call it the watershed. Lawyers call it jurisdiction. Doctors call it the standard of care. Architects call it the foundation. Operating systems call it the runtime.
- Names
- 18
- Clusters
- 3
- Formulations
- 4
These are not metaphors for the same concept. They are the same concept, discovered independently across centuries and disciplines. The pattern repeats at every scale — what mathematicians would call a fractal structure. The same governing logic appears whether you are managing water rights in a high-desert valley or managing authority in an autonomous AI deployment.
KTP provides the formal language that unifies them — and applies that language to autonomous digital systems for the first time. If you already work in one of these domains, you already understand the concept. You may just not have seen it applied here yet.
The framework has unusual political portability because the concept it names is already present in every governance tradition. You do not need to adopt new vocabulary. You need to recognize that the vocabulary you already use in your domain applies here — and that the domain in question is one that does not yet have a substrate specification.
Four formulations that survive translation
- 01Substrate, not policy. Physical and architectural systems enforce constraints that no policy can. We have been writing policy. We need to specify substrate.
- 02Authority cannot exceed what the environment can hold. This is not a value statement. It is a law.
- 03You cannot legislate trust into existence — you can only design the substrate that allows it to form.
- 04We have been regulating agent behavior. We need to regulate agent substrate.






