Specifications¶
The complete technical blueprint for Digital Physics
The KTP specification suite defines every aspect of the protocol—from cryptographic primitives to governance mechanisms. These documents are the authoritative reference for implementers, auditors, and researchers.
-
RFCs on GitHub
27 Request for Comments documents covering every protocol component. Browse the source.
-
Blue Zones
Architectural patterns for creating safe, bounded trust environments.
-
Schemas
JSON schemas for Context Tensors, Trust Proofs, and other core data structures.
Choose Your Path¶
Different readers need different entry points. Select the journey that matches your goals:
🏗️ Implementer's Path
Building a KTP-compliant system? Follow this sequence:
Foundation → Identity → Environment → Compliance
🔍 Auditor's Path
Validating a KTP implementation? Focus on these areas:
Compliance → Security → Governance
🎓 Researcher's Path
Understanding the theory behind Digital Physics? Explore:
Philosophy → Mechanics → Innovation
- KTP-Core (Sections 1-4) → Constitution
- KTP-Tensors → KTP-Gravity → KTP-Signal
- KTP-Oracle → KTP-Celestial
Specifications by Domain¶
The bedrock protocols that define KTP's core architecture.
| Specification | Status | Description |
|---|---|---|
| KTP-Core | Stable | The Zeroth Law, Trust Scores, A ≤ E constraint |
| KTP-Crypto | Stable | Cryptographic primitives and algorithms |
| KTP-Transport | Stable | Network transport and messaging protocols |
| KTP-Identity | Stable | Vector Identity and trajectory-based authentication |
Start Here
If you're new to the specifications, begin with KTP-Core. It establishes the foundational concepts that all other RFCs build upon.
How trust is measured, computed, and flows through the system.
| Specification | Status | Description |
|---|---|---|
| KTP-Tensors | Stable | Context Tensor specification (1,707 dimensions) |
| KTP-Gravity | Draft | Digital Gravity enforcement mechanisms |
| KTP-Signal | Draft | Trust signal propagation and analysis |
| KTP-Relational | Draft | Agent-to-agent trust relationships |
| KTP-Oracle | Experimental | Trust oracles and external attestation |
Understanding Trust Flow
Trust in KTP flows through a measurement → computation → enforcement pipeline:
- Tensors capture the 1,707-dimensional environmental state
- Signal propagates trust changes through the network
- Gravity enforces constraints as agents approach limits
- Relational tracks inter-agent trust dynamics
Where agents operate and how trust boundaries are established.
| Specification | Status | Description |
|---|---|---|
| KTP-Zones | Draft | Blue Zone architecture and governance |
| KTP-Federation | Draft | Cross-domain trust federation |
| KTP-Sensors | Draft | Environmental sensor requirements |
| KTP-Celestial | Experimental | Universal time and coordination |
The Zone Gradient
Environments range from maximum constraint to no enforcement:
- Deep Blue: Maximum constraint, cryptographic guarantees
- Blue: High constraint, monitored operations
- Cyan: Moderate constraint, verified agents
- Green: Light constraint, basic verification
- Wild: No KTP enforcement
Rules, oversight, and compliance mechanisms.
| Specification | Status | Description |
|---|---|---|
| KTP-Governance | Draft | Protocol governance and amendment |
| KTP-Human | Stable | Human oversight requirements |
| KTP-Enforce | Draft | Enforcement mechanisms |
| KTP-Conformance | Stable | Conformance testing requirements |
| KTP-Audit | Stable | Audit trail and non-repudiation |
Governance Hierarchy
KTP governance follows a clear hierarchy:
- Constitution — Immutable foundational law
- Core RFCs — Stable specifications requiring deprecation process
- Extended RFCs — Evolving specifications under active development
- Implementation Guidance — Non-normative best practices
Evolution, resilience, and system maintenance.
| Specification | Status | Description |
|---|---|---|
| KTP-Migration | Draft | Version migration protocols |
| KTP-Recovery | Draft | Trust recovery after incidents |
| KTP-Emergency | Draft | Emergency response procedures |
| KTP-Deprecation | Stable | Deprecation and sunset process |
| KTP-Legacy | Draft | Legacy system integration |
| KTP-Provenance | Draft | Model and data provenance tracking |
Lifecycle Principles
KTP systems must plan for change:
- Migration: Smooth transitions between protocol versions
- Recovery: Rebuilding trust after compromise
- Emergency: Rapid response to active threats
- Deprecation: Graceful retirement of old features
Threat modeling and security analysis.
| Specification | Status | Description |
|---|---|---|
| KTP-Threat-Model | Stable | Comprehensive threat analysis |
| KTP-Problems | Draft | Known issues and mitigations |
| KTP-Privacy | Draft | Privacy-preserving computations |
Security Considerations
Every KTP implementation must address:
- Gaming: Agents attempting to inflate trust scores
- Collusion: Coordinated attacks across agent networks
- Sybil: Fake identity proliferation
- Oracle Manipulation: Corrupting external trust sources
Specification Status Guide¶
| Status | Icon | Meaning |
|---|---|---|
| Stable | Production-ready. Breaking changes require formal deprecation process. | |
| Draft | Under active development. May change significantly before stabilization. | |
| Experimental | Research stage. Not recommended for production use. |
Context Tensor Schema¶
The Context Tensor is the core data structure for trust decisions. Below is a high-level view of its schema structure.
| Field | Type | Description |
|---|---|---|
tensor_id |
UUID | Unique identifier for this tensor instance |
timestamp |
ISO8601 | When this tensor was calculated |
e_score |
Float (0-100) | The final Experience Score |
arq_vector |
Object | The raw ARQ dimensions |
arq_vector.accessibility |
Float (0-1) | Availability of the resource |
arq_vector.retainability |
Float (0-1) | Stability of the connection |
arq_vector.quality |
Float (0-1) | Fidelity of the interaction |
risk_deflation |
Object | Risk factors applied |
risk_deflation.security |
Float (0-1) | Security penalty |
risk_deflation.compliance |
Float (0-1) | Compliance penalty |
For the full JSON schema definition, see context-tensor.json.
Quick Reference¶
Most Referenced
Complete RFC Index
For a flat listing of all specifications, visit the GitHub RFC directory.
Where to Go Next¶
-
Deep Dive: Blue Zones
Understand the architecture of trust environments in detail.
-
Data Structures
Explore the JSON schemas that define KTP's core data formats.
-
Back to Basics
Need a conceptual refresher before diving into specs?
-
Start Building
Ready to implement? Get the developer guide.