KTP/
github ↗
created 14 October 2026 · last modified 14 October 2026
named controls for a public framework

Canon.

Canon is the framework's self-governance layer. What the work is and what it is not. Which claims are theses, which are hypotheses, which are operational protocols. What would falsify each. What KTP must never become. What the writing promises readers about how it uses cognitive force.

Built so the work can scale without becoming the thing it diagnoses. Trust infrastructure for a framework about trust infrastructure.

§01the minimum viable canon

Eight sentences. The ones that must remain stable while everything else evolves. Small enough to remember; strong enough to defend.

01Trust is infrastructure.
The public thesis.
02Correction is not repair.
The repair thesis.
03Verification is not trust.
The enterprise / security distinction.
04The payload changes; the pipeline does not.
The cognitive-domain insight.
05If you open vulnerability, return an instrument.
The ethical rule.
06A trust score is not trust.
The KTP / dashboard guard.
07Discernment, not paranoia.
The reader-side discipline.
08Build the container before the signal scales.
The governing principle.

§02in canon

the rationale

Synthesis Report — Lineage and Launch

Two-and-a-half-millennia of intellectual lineage on one side; the public-exposure forecast on the other. The document that explains why canon exists and what the framework is being held against.

open →
the lineage operational

Canon Clusters

Six clusters of intellectual lineage the framework draws from — Predictive Processing, Critical Theory, Mycelial Networks, Complexity Science, Complexity Economics, Improvisation Traditions. Each named with its public phrase, anchored figures, member concepts, and the citation cautions that travel with it.

open →
architecture

The Canonical Stack

Seven named layers — Digital Gravity, Relational Trust Infrastructure, Trust Force, Ostrom-Percolation, Reconciliation Dynamics, KTP, Tamed Autonomy. The pieces are connected; they are not interchangeable.

open →
claims

Claims Register

Every claim the program makes, sorted by maturity level (L1 thesis through L6 operational protocol), with the evidence behind it and what would weaken it. Named because the program wants those tests to happen.

open →
boundaries

What This Is Not + KTP Red Lines

Seven clauses naming what the framework is not — not social credit, not censorship, not anti-AI, not paranoia. Plus the ten non-negotiable red lines for any KTP implementation.

open →
vocabulary

Glossary

Pinned definitions across foundational, KTP, CDO, cluster, and Phase 5/6 vocabulary. Verification is not trust. Correction is not repair. The glossary exists so the phrases can travel without detaching.

open →
ethics

Ethical Boundary

If the essay opens vulnerability, it must return an instrument. The house rule that distinguishes the work from the operation it diagnoses, plus the anti-paranoia clause that keeps discernment from collapsing into suspicion.

open →
repair surface

Repair

Version history, corrections, retired claims, source corrections, and open questions. A theory about repair cannot hide its own corrections; this is the framework's own repair path, kept visible.

open →

§03canon-adjacent

Three pages perform a canon function but live under /research because the program proper holds them there. Cross-linked rather than duplicated.

Falsification

/research/falsification

The empirical face of the claims register: each falsifier is a pre-registrable prediction whose failure would force revision.

Methods

/research/methods

How the work is done — reproducibility, scoring, the case-recoding gate, and the risks the program is tracking publicly.

Cartography

/research/cartography

The graph as terrain. Tensions held open in the graph correspond to claims still in motion in the canon.

§03bancestors

People whose work the framework treats as structurally upstream. Each entry earns its claim through a specific inheritance — what the framework borrows, named in the open. Not citations. Receipts.

Stewart Brand
live

Pace layers, maintenance as propagation mechanism, the WEC ↔ Installed Watcher inversion. The framework's structural ancestor for installed-perceptual-organ pedagogy.

Eric Hoffer
forthcoming

Mass movements that consume their own conditions of possibility. Substrate depletion in political register. Original phrasing of maintenance as the essential art of civilization.

Elinor Ostrom
forthcoming

Eight design principles for commons that survive. The framework's ninth principle (temporal-edge persistence) sits as continuation, not correction.

Donella Meadows
forthcoming

Twelve leverage points for intervening in a system. The framework's posture toward where to push when systems are misbehaving.

Stuart Kauffman
forthcoming

The adjacent possible. Why some moves in design space are reachable from where you are and most are not. Substrate as the set of currently-reachable adjacencies.

§04how to read this work

The framework's posture toward its own reading. Eight statements that travel together — none stands alone.

  1. 01These essays are diagnostic instruments.
  2. 02They may begin with vulnerability.
  3. 03They should return an instrument.
  4. 04Not every signal is hostile.
  5. 05Correction is not repair.
  6. 06Trust is not a score.
  7. 07The research program is modular and still developing.
  8. 08The goal is discernment, not paranoia.
How to cite
APA 7th ed.

Perkins, C. (2026, May 7). Canon — framework self-governance layer. Kinetic Trust Protocol. https://kinetic-trust-protocol.net/canon
reference
pending — source not yet published
RFC tree on GitHub ↗