Concept KernelProtocol v3.7

10 parts. 48 chapters. Three loops. BFO-grounded ontology. Claude integration. Consensus governance. PROV-O provenance. The full specification for concept-driven development.

Introduction

Operator

Join Discord

🔄

Three Loops (CK / TOOL / DATA)

Identity is read-only. Tools execute. Data accumulates. The separation axiom enforced from volume mounts to agent prompts.

🧬

BFO 2020 Grounding

Every kernel is a BFO:0000040 Material Entity. Every action is an Occurrent. The ontology is not a label -- it is the type system.

🔗

5 Edge Predicates

COMPOSES, TRIGGERS, PRODUCES, CONSUMES, EXTENDS -- the five relationships that connect kernels into a typed fleet graph.

✅

20 Compliance Checks

CK.ComplianceCheck validates identity, ontology, SHACL, edges, NATS, provenance, and more. Every kernel carries a proof record.

🏛️

CK.Consensus Governance

Propose, evaluate, approve. Four validation layers. Tasks generated for headless Claude execution. Every decision is a prov:Activity.

🔍

PROV-O Provenance

Every instance traces back through action, kernel, task, and goal. Three mandatory fields. Enforced by check.provenance.

🤖

Claude as Subagent

/ck spawns a Claude Code subagent loaded with a kernel's CK loop. EXTENDS mounts Claude capability. Streaming via NATS.

📊

Ontological Graph

Jena Fuseki /ckp dataset. SPARQL-queryable fleet. BFO-typed nodes. Named graphs per project.