KTP/
github ↗
created 14 October 2026 · last modified 14 October 2026
external work read against the frame

Prior Art.

This is not the program's own register — that is Papers. This is the shelf of outside instruments the program has read against the frame: treaties, statutes, standards, and protocols that touch the territory the framework claims. Thinkers and traditions arriving at the framework's claims are a different surface — the Convergences table on Cartography. Instruments here, witnesses there.

The discipline is a single rule: convergence is not confirmation. When an outside instrument lands on a structure the framework already names, that is a witness worth recording — and the honest entry names where the mapping stops, not only where it holds. Each read below is a claim a skeptical reader can check against the source. The comparison matrix scores KTP by the same rubric as everything else, and the page ends with the program's own open problems, because a register of other people's limits that omitted ours would be marketing.

Computational trust models — Marsh, Jøsang, EigenTrust, FIRE — are deliberately absent here: they are the formal comparison targets of Paper 3 and live in Papers, where the comparison carries submission-grade obligations.

Approve-once instruments: assess risk, set principles, impose obligations, audit for compliance. Authority is fixed at design, ratification, or market entry, and never recomputed along the path. These make governance in motion legible by contrast — and they are complements, not competitors: the at-rest layer is where legitimacy comes from.

PA1governance-at-rest exemplar · juridical witness to A ≤ E
Artificial Intelligence, Human Rights, Democracy, and the Rule of Law: A Primer
Leslie, Burr, Aitken, Cowls, Katell & Briggs · 2021 · Council of Europe / The Alan Turing Institute
relation to the frame

Maps nine principles to ECHR-anchored rights and Member-State obligations, then audits for compliance. Authority is fixed at design and procurement time and never recomputed along the path — the cleanest citable statement of governance at rest.

the read

Excellent primer, dated paradigm. It converges partway onto A ≤ E from human-rights law with zero physics, then stops exactly where trajectory would be needed. The convergence is real and Level-3; the regime boundary — decision-tempo ÷ oversight-tempo — is nameable and is the whole story.

PA2binding successor to PA1 · first international AI treaty
Framework Convention on Artificial Intelligence
Council of Europe · 2024 · CETS No. 225, opened for signature September 2024
relation to the frame

The treaty the primer's lineage produced: CAHAI → CAI → a framework convention binding on ratifying states. It closes the arc PA1 opened — the same rights-obligations-audit architecture, now with treaty force.

the read

Historic and still at rest. Binding force changes who must comply, not when authority is computed: obligations attach to states at ratification and to systems at deployment, with no primitive for standing that accumulates or decays along an agent's path. The strongest possible version of approve-once — which is exactly what makes it the right legitimacy layer for a motion protocol to sit under.

PA3approve-once at market scale
EU Artificial Intelligence Act
European Parliament & Council · 2024 · Regulation (EU) 2024/1689
relation to the frame

Risk tiers, conformity assessment, CE marking, market surveillance. The canonical industrial-scale form of governance at rest: authority is granted at market entry on a static risk classification, re-checked by audit and post-market monitoring.

the read

The biggest foil in the room. Its own Article 72 post-market monitoring concedes the static assessment decays — but the remedy is periodic human-tempo review, not recomputed authority. For general-purpose and agentic systems the risk-tier ontology is already straining: the Act classifies products, and an agent is a path, not a product.

PA4voluntary at-rest · gestures at continuity
NIST AI Risk Management Framework 1.0
National Institute of Standards and Technology · 2023 · NIST AI 100-1
relation to the frame

Govern / Map / Measure / Manage, iterated across the lifecycle. The most motion-aware of the foils: it names continuous risk management and post-deployment monitoring as first-class functions.

the read

Gestures at governance in motion without the primitive that would deliver it. 'Manage' loops at organizational tempo — reviews, updates, documentation — and risk attaches to the system-in-context, not to an accumulating worldline. Voluntary adoption also means no enforcement floor. Closest at-rest neighbor; still at rest.

PA5the values root of the at-rest family
OECD AI Principles
OECD Council · 2019 / 2024 · OECD/LEGAL/0449, amended 2024
relation to the frame

The shared upstream: the first intergovernmental AI standard, adopted by 40+ countries and echoed by the G20. The primer cites it; the AI Act and the Framework Convention inherit its vocabulary of trustworthy, human-centred AI.

the read

Values without an authority model — deliberately. Its function is coordination, and it performs it: the whole at-rest family speaks its language. Nothing in it prevents a motion architecture; nothing in it provides one. Root of the family tree, not a rival.

The honest lineage. Places where authority already attenuates, delegates, or re-decides along the path. These matter more than the foils intellectually: admitting where the motion already exists is what keeps the framework from overclaiming novelty.

PA6ancestor and foil at once · per-request re-decision
Zero Trust Architecture (SP 800-207)
Rose, Borchert, Mitchell & Connelly (NIST) · 2020 · NIST Special Publication 800-207
relation to the frame

'Never trust, always verify': no implicit trust from network location; every access decision re-evaluated per request against identity, device posture, and context signals. The security tradition's own admission that approve-once fails.

the read

The closest mainstream position, and the one the protocol must own its relation to. Zero Trust re-decides continuously but from a memoryless posture — each request is scored against current signals, and nothing accumulates. Deny-by-default without a path back to earned standing is wayfinding with no map of where you have been. Motion without trajectory; the protocol is what happens when the re-decision loop is given a worldline.

PA7closest technical ancestor · authority attenuates along the path
Macaroons: Cookies with Contextual Caveats
Birgisson, Politz, Erlingsson, Taly, Vrable & Lentczner (Google) · 2014 · NDSS 2014
relation to the frame

Bearer tokens whose caveats attenuate authority as they are delegated downstream — including third-party caveats that require external attestations. Authority genuinely narrows along the delegation path, cryptographically, at machine tempo.

the read

The strongest single ancestor: the one mechanism in deployed practice where the path itself modifies authority. The boundary is exact — caveats attenuate monotonically and never recompute. A macaroon's authority can only shrink from its mint; nothing observed along the path can restore, expand, or re-derive it. Attenuation is motion in one direction; trajectory-native standing moves in both.

PA8the substrate the authority model descends from
Object-Capability Security
Mark S. Miller · 2006 · Robust Composition (PhD thesis, Johns Hopkins); E language; seL4 lineage
relation to the frame

Authority as unforgeable, delegable, attenuable reference — no ambient authority, permission by possession, confinement by construction. The formal foundation under macaroons, capability-secure kernels, and every serious least-authority architecture since.

the read

Ancestor in the strict sense: the protocol's authority algebra is capability discipline plus a time axis. What ocap lacks is not rigor but history — a capability's provenance is not part of its meaning, so an agent's accumulated conduct cannot bear on what it may do next. Endowment at creation, attenuation at delegation, and nothing in between. The gap between a reference and a worldline is the entire research program.

What is actually shipping for autonomous agents right now, and what its authority model is. The interval between these instruments and trajectory-native authorization is the gap the protocol positions into.

PA9identity-as-issued-credential · the thin-proxy foil
W3C Verifiable Credentials & Decentralized Identifiers
W3C VC Working Group · 2022 / 2025 · DID Core 1.0 (2022); VC Data Model 2.0 (2025)
relation to the frame

Identity as a portfolio of issuer-signed claims resolved through decentralized identifiers. The strongest available statement of credential-based identity — decentralized, cryptographic, revocable via status lists.

the read

The thin proxy, stated in its best form. Everything an agent IS, on this model, is something an issuer once said about it — issuance is the cold-start story and also the theft surface, since anything issued can be replayed and anything held can be stolen. A witnessed worldline is accumulated, not issued; there is no credential to steal because there is no credential. VCs remain the right rail for claims that ARE attestations; they cannot carry standing.

PA10agent interop shipping with thin auth
Model Context Protocol & Agent2Agent
Anthropic (MCP); Google et al. (A2A) · 2024 / 2025 · modelcontextprotocol.io; A2A Project (Linux Foundation)
relation to the frame

The de-facto wiring of the agent economy: tool access and agent-to-agent delegation over standardized transports, authenticated with OAuth-style tokens and declared capability cards.

the read

Interop arrived before authority. Both protocols solve connection and leave authorization at bearer-token granularity: any agent holding the token is the agent, at machine tempo, across compositions no human reviews. This is the tempo regime where approve-once fails fastest and the surface where a trajectory-native control plane is least optional. The gap is not a criticism of MCP or A2A — transport should not carry governance — but the gap is real, current, and compounding.

PA11detection-based control · the rival bet
An Approach to Technical AGI Safety and Security (AI Control Roadmap)
Google DeepMind · 2026 · DeepMind technical roadmap
relation to the frame

The most rigorous published plan for controlling misaligned agents: monitoring, capability tiers, and a prevention guarantee gated on catching deceptive behavior before it completes.

the read

The serious rival position — control through detection rather than authorization. Its own D4 tier names where detection fails; the capability–mitigation ladder is A ≤ E unnamed; and monitoring feeds alarms, not standing. Where the roadmap races to catch what an agent is doing, trajectory-native authorization bounds what it was ever empowered to do. Full engagement on the dedicated page.

KTP and the register, scored on six dimensions. KTP is judged by the same rubric as everything else — its weak cells cite the problem register below by number. A starred value carries a note; hover (or long-press) to read it. The dimensions:

  • motionAuthority recomputed in motion — does standing change along the path, or is it fixed at approval?
  • trajectoryIdentity as trajectory — is an agent its accumulated, witnessed history, or an issued credential?
  • tempoMachine-tempo native — do decisions execute at the speed agents act, without a human in the loop?
  • bindingBinding enforcement — is compliance compelled (cryptographically or legally), or voluntary?
  • cold-startCold-start / delegation story — how does a new agent acquire authority, and how does authority delegate?
  • revocationRevocation vs attenuation — can granted authority be recalled along the path, or only narrowed at grant time?
instrumentmotiontrajectorytempobindingcold-startrevocation
KTPyes*yes*yes*partial*partial*yes*
CoE/Turing Primer (2021)nononono*no*partial*
CoE Framework Convention (2024)nononopartial*nopartial*
EU AI Act (2024)no*no*noyes*no*partial*
NIST AI RMF (2023)partial*nonono*nono
OECD Principles (2019/24)nononono*nono
Zero Trust / SP 800-207 (2020)partial*no*yespartial*no*yes*
Macaroons (2014)partial*noyesyes*partial*partial*
Object-capabilities (2006)partial*no*yesyes*partial*partial*
W3C VCs / DIDs (2022/25)no*no*yespartial*yes*partial*
MCP / A2A (2024/25)no*noyesno*no*partial*
AI Control Roadmap (2026)partial*no*yespartial*noyes*

KTPScored by the same rubric as the register, honestly: cultural trust relativism is OPEN (RFC #12), the observer-effect state-perturbation question is OPEN (RFC #1b), and no system can prove its own trustworthiness from the inside. The full problem register is below.

Instrument-level honesty, to match what the register demands of everyone else. What the framework is not — not social credit, not censorship infrastructure, and the red lines it must never cross — is a different page: Limits. This section is about capability.

does
Recompute authority along the path

Authorization is a function of trajectory and environment, evaluated continuously — governance in motion rather than approve-once.

Treat identity as worldline

An agent is its accumulated, witnessed history. No trajectory, no standing, default deny. Credentials are proxies the protocol can consume but never mistakes for the agent.

Bound autonomy by the environment

A ≤ E: permitted autonomy never exceeds the environment's demonstrated capacity to bound it. Enforcement is a comparison, not a committee.

Operate at machine tempo

Trust calculation runs asynchronously; enforcement is an integer comparison at request time. The tempo regime where at-rest instruments fail is the protocol's home regime.

doesn't
Replace law, treaty, or legitimacy

The at-rest layer — conventions, statutes, principles — is where authority to govern comes from. The foils above are complements: KTP is a control plane that needs a constitution above it.

Solve cultural trust relativism

What counts as trustworthy conduct is not culturally invariant, and the protocol does not pretend otherwise. RFC problem #12, state: OPEN — the register's honest floor.

Eliminate its own oracle risk

Threshold cryptography distributes the oracle; it does not delete it. RFC problem #5, state: MITIGATED — reduced, not gone.

Prove its own trustworthiness from the inside

No system can. The protocol's genesis bottoms out in an externally accountable root, and the research program treats that as a feature of honesty, not a defect of design.

Publish the full trust equation

The public surface carries the simplified Trust Score and the named relational conditions; the full instrumented form is held in private research until the scoring protocol clears external coding.

The register above names where every other instrument stops. This table names where this one does. Twenty-two problems from the KTP-Problems RFC — known limitations, anticipated critiques, and open questions — with the solution state the program actually claims, not the one it would prefer. The RFC treats each as an invitation to collaboration; the full text carries the critique, the current response, and the expertise each problem needs.

#problemdomainstateprimary gap
1Heisenberg Penalty (latency)PerformanceSOLVEDOptimization only; the state-perturbation half (§1b) remains open as TFE prediction #24
2Hypervisor Opaque WallArchitectureBOUNDEDCloud provider attestation APIs
3False Positive FatalityEthicsMITIGATEDEthics of the tradeoff remains external
4Baseline PoisoningSecurityMITIGATEDDetection research
5Oracle RiskSecurityMITIGATEDFormal verification
6Standard Oil MonopolyGovernanceEXTERNALGovernance / community
7Legal Black BoxLawEXTERNALLegal precedent
8Quantum CliffCryptographyBOUNDEDPQC standardization
9Agent CollusionGame TheoryMITIGATEDGraph analysis
10Jurisdictional FragmentationLaw / PolicyEXTERNALInternational law
11Time Oracle AttackSecurityMITIGATEDTime source security
12Cultural Trust RelativismSociologyOPENAnthropology / ethics
13Bootstrap ParadoxArchitectureSOLVEDIAL3 + genesis ceremony
14Sensor SaturationSecurityMITIGATEDDoS research
15Surveillance Infrastructure RiskPrivacy / GovernanceMITIGATED+Governance required
16Privacy-Trust ParadoxPrivacyMITIGATEDTheoretical limits
17Function CreepGovernanceMITIGATED+Eternal vigilance
18Right to be ForgottenLawBOUNDEDLegal interpretation
19Cross-Border PrivacyLaw / PolicyEXTERNALJurisdictional law
20Behavioral FingerprintingPrivacy / SecurityMITIGATEDResearch needed
21Goodhart AbyssMeasurement / TheoryMITIGATED+Theoretical limits
22Cultural BedrockSociologyPARTIALOngoing consultation
legend
SOLVEDarchitectural or mathematical solution exists
BOUNDEDfailure mode constrained to acceptable scope
MITIGATEDrisk reduced but not eliminated
MITIGATED+technical mitigations + governance/policy required
PARTIALsome aspects addressed, fundamental limits remain
EXTERNALrequires expertise outside computer science
OPENno satisfactory solution yet
Problems 15, 17, and 21 require ongoing vigilance rather than a one-time fix; problem 3 is technically mitigated while its ethical tradeoff remains external. What would falsify the theory itself is a different register — Falsification.
How to cite
APA 7th ed.

Perkins, C. (2026, July 1). Prior Art. Kinetic Trust Protocol. https://kinetic-trust-protocol.net/research/prior-art
Plain text

Chris Perkins, "Prior Art," Kinetic Trust Protocol, https://kinetic-trust-protocol.net/research/prior-art (accessed July 1, 2026).
full specification
rfcs-txt/ktp-problems.txt
Read KTP-Problems ↗