Skip to content
clawkernel mascot clawkernel

NanoBot

NanoBot version: audited against commit 30361c9
CKP version: 0.3.0
Assessment mode: manifest baseline

Result

Section titled “Result”

NanoBot does not currently expose a native CKP stdio JSON-RPC transport, so the current assessment is manifest-only.

  • L1: 4/13 pass
  • L2: 1/10 pass
  • L3: 1/8 pass
  • Overall: L1 PARTIAL

The skipped vectors are transport-dependent runtime checks, not manifest failures.

Evidence

Section titled “Evidence”

Why It Is Partial

Section titled “Why It Is Partial”

The audited NanoBot runtime has orchestration and MCP integration, but not a native CKP lifecycle/tool transport.

  • no native claw.initialize / claw.status / claw.shutdown endpoint was identified
  • the existing bridge layer is not CKP stdio JSON-RPC
  • manifest structure maps well enough to CKP for baseline validation

Next Step

Section titled “Next Step”

To convert NanoBot from baseline compatibility to live CKP conformance, the project needs a CKP bridge that maps lifecycle, tool, memory, and swarm methods onto its runtime internals.

See Compatibility overview for side-by-side results.