The Protocol
KCP is a portable, textual, extensible knowledge representation protocol. It is human-auditable, AI-optimized and source-traceable.
Design Principles
File Extension
The canonical extension is .kcp. Recommended encodings: .kcp.md (Markdown), .kcp.yaml (YAML), .kcp.json (JSON).
Core Objects
- — Package Metadata
- — Knowledge Nodes
- — Relations
- — Rules
- — Procedures
- — Triggers
- — Chunks
- — Atomic Units
- — Agent Instructions
- — Source Traceability
Source Basis Labels
Every extracted item must be marked with one of the following labels.
Directly stated in the source.
Reasonably inferred from source content.
Created by combining multiple source fragments.
Represents the source author's subjective claim.
Weakly supported or ambiguous.
Implicit prose vs labeled claims
Source basis labels exist so every claim carries its own evidence type. Compare a human paragraph (sources implied) with a .kcp fragment (sources tagged).
Good for humans
According to the internal manual, refunds above $500 generally require manager approval. The team also believes that responding within 2 hours improves retention, though this hasn't been formally measured. Some agents add that loyal customers tend to forgive delays — anecdotally.
.kcp · Labeled and traceable
claim: refunds > 500 require manager approvalsource_basis: explicitconfidence: 0.96source: internal_manual#sec-4.2claim: response under 2h improves retentionsource_basis: inferredconfidence: 0.55claim: loyal customers forgive delayssource_basis: author_opinionconfidence: 0.40claim: response time correlates with NPSsource_basis: synthesizedconfidence: 0.62claim: agents share this folkloresource_basis: uncertainconfidence: 0.30
Confidence Scores
Use a 0.00–1.00 scale.