KTP/
github
Brown water churns below red sluice gates in a concrete channel under a blue sky
Understand · one concept, many names

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.

Agriculture & WaterWatershedThe terrain that determines where water flows, which communities share a resource, and what the physical land enforces without a regulator.A ≤ E — Autonomy Cannot Exceed EnvironmentRead the dossier →Law & JusticeJurisdictionThe preconditions that determine whether a legal action is cognizable at all — not what you are allowed to do, but whether the system will hear the claim.Trust Tiers / Environmental EnforcementRead the dossier →Medicine & Public HealthStandard of CareThe conditions under which a clinical judgment is considered trustworthy — not what the physician decides, but the environment in which the decision is made.Soul Constraint / Environmental EnforcementRead the dossier →EducationLearning EnvironmentThe conditions — stability, safety, appropriate challenge — that make a learner's potential accessible. Not what is taught, but what makes learning possible.A ≤ E / Substrate as PreconditionRead the dossier →Community & Shared ResourcesThe CommonsThe rule-structure, boundaries, and norms that make a shared resource sustainable across time — what Elinor Ostrom called the substrate of collective action.Ostrom Principles as Substrate SpecificationRead the dossier →Architecture & ConstructionFoundationThe load-bearing structure that everything else rests on — what cannot be removed without collapse, and what determines what changes above it can safely be made.Layer 0 / Substrate as Load-bearing PrimitiveRead the dossier →Finance & MarketsMarket MicrostructureThe matching engine, clearing mechanism, and settlement rules that make a price meaningful — not what traders decide, but the conditions under which trading has predictable consequences.Environmental Enforcement / Trust AnchorRead the dossier →Ritual & Cultural PracticeSacred Space / LiturgyThe ritual conditions — time, location, sequence, witness — that make certain kinds of exchange meaningful and binding. Not what is said, but the conditions under which saying it means something.Substrate as Precondition for EncounterRead the dossier →Networking & CommunicationsProtocol StackThe layered rules — TCP/IP, HTTP, TLS — that determine whether data arrives intact, not what data is sent.Layer 0 / Environmental EnforcementRead the dossier →Operating SystemsRuntime EnvironmentThe kernel-level conditions — memory boundaries, process permissions, interrupt handling — that determine what any program on the system can physically do.A ≤ E / Environmental EnforcementRead the dossier →AI & Autonomous AgentsDeployment EnvironmentThe conditions under which an AI system operates: what it can remember across sessions, whose authority it recognizes, what can correct it, and which actions it can take without confirmation.All KTP Primitives — The Missing SubstrateRead the dossier →Cryptography & PKITrust AnchorThe root certificate or key infrastructure from which all trust chains derive — a single upstream architectural decision that determines what every downstream system can assume.Vector Identity / Layer 0Read the dossier →Security & Zero TrustAttack SurfaceThe structural sum of points where an adversary can enter or extract — a property of the system's architecture, not of its behavior or intentions.A ≤ E / Environmental EnforcementRead the dossier →Databases & Data ArchitectureSchemaThe structural constraints — types, relationships, integrity rules — enforced at the data layer before any application logic runs.Soul Constraint / Environmental EnforcementRead the dossier →Constitutional LawConstitutional OrderThe foundational structure that determines what laws are legitimate — not what laws say, but the conditions under which lawmaking itself is valid.The Constitution of Digital Physics / Layer 0Read the dossier →International RelationsRules-Based OrderThe treaty infrastructure, multilateral institutions, and shared norms that make state commitments credible — not what states are permitted to do, but the conditions under which their commitments mean anything.Trust Tiers / Vector IdentityRead the dossier →Administrative Law & RegulationDue ProcessThe procedural conditions that must be met before a government action against a person is legitimate — not the outcome of the decision, but the architecture of how decisions are made.Flight Recorder / Environmental EnforcementRead the dossier →Land Use & Urban PlanningZoningThe prior conditions that determine what can be built where — not regulations on what buildings do, but architectural constraints on what buildings can be.A ≤ E / Pre-commitment ConstraintRead the dossier →
For policy readers

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

  1. 01Substrate, not policy. Physical and architectural systems enforce constraints that no policy can. We have been writing policy. We need to specify substrate.
  2. 02Authority cannot exceed what the environment can hold. This is not a value statement. It is a law.
  3. 03You cannot legislate trust into existence — you can only design the substrate that allows it to form.
  4. 04We have been regulating agent behavior. We need to regulate agent substrate.

Keep learning the language

How to cite
APA 7th ed.

Perkins, C. (2026, May 6). The Common Names: Substrate Across Domains. Kinetic Trust Protocol. https://kinetic-trust-protocol.net/language
Plain text

Chris Perkins, "The Common Names: Substrate Across Domains," Kinetic Trust Protocol, https://kinetic-trust-protocol.net/language (accessed November 15, 2026).
Page created 7 May 2026 · last modified 2026-10-30