Documentation

Protocol Architecture

System map of the Network — layers, boundaries, and data flows without implementation topology.

1. Layer Model

┌─────────────────────────────────────────────┐
│  Client Layer — Nodes, devices, Vault keys    │
├─────────────────────────────────────────────┤
│  Gateway — TLS, auth, KARP rate governance    │
├─────────────────────────────────────────────┤
│  Coordination — KSMP, KSMP v3, KVCP realtime  │
├─────────────────────────────────────────────┤
│  Intelligence — KCAP, KSRP, KDRP, KEVP        │
├─────────────────────────────────────────────┤
│  Persistence — graph, corpus, policy state    │
├─────────────────────────────────────────────┤
│  Signal — KSPP async interaction ingest       │
└─────────────────────────────────────────────┘

2. Plaintext Boundary

Public posts and profile metadata live in the persistence layer. Encrypted communications exist only as ciphertext at coordination and persistence layers. KMSP and KSLP scan public content only — never KSMP bodies.

3. Post-Create Pipeline

Post Created
  → KLDP   language / script
  → KEVP   semantic embedding
  → KMSP   safety scan
  → KSLP   link check
  → persist (policy_state)
  → eligible for KCAP candidate pools

4. Feed Request Pipeline

GET /feed/{surface}
  → KCCP cache
  → KCAP (SI → CG → FE → MS → TF → FR)
  → impression log
  → response

5. Protocol Registry

Institutional charters for every published instrument live under Protocol Registry. Developer references on this docs site describe integration contracts; charters describe governance guarantees.

← Back to docs home