KnotenCore is a high-performance, headless Rust runtime and P2P mesh engine for autonomous AI agents. Built with zero-trust cryptographic peering, quorum-gated governance, and sandboxed VM isolates — driven by structured JSON-AST.
If terms like "CRDT Anti-Entropy", "Ed25519 Quorum Governance", and "Register VM" sound like alien hieroglyphs: Here is the 60-second explanation for humans.
Large Language Models (like GPT or Claude) are brilliant at thinking and drafting plans. But you wouldn't give an architect a sledgehammer to smash walls unsupervised.
AI agents can make errors—generating runaway recursion or attempting to exhaust host memory.
Complex workflows require multi-agent cooperation across networks, exchanging state and delegating subtasks.
Every layer is purpose-built to eliminate ambiguity, enforce boundaries, and survive adversarial mesh conditions.
knc_store_digest) via ring and lean differential sync (knc_store_diff) minimizing network overhead.knc_mesh_peers?action=gossip).IsolateQuota: instruction gas metering, memory watchdog, call depth limits, and live isolate hot-reloading.additionalProperties: false, error catalog with self-healing hints, and anti-pattern guide for LLMs.Continuous security sprints systematically audit and eliminate attack surfaces. The codebase enforces zero-panic error isolation across all transport, consensus, and execution paths.
-32001.try_clone() error isolation and stream teardown.ring::digest::SHA256 state digests allow nodes to verify consistency and exchange only delta entries.Zero-Trust Ed25519 & HMAC-SHA256 auth-gated. All endpoints accessible via TCP (port) or WebSocket (--ws-port) transport.
Strictly separated, circular-dependency-free. JSON-AST in, bytecode out, mesh on the wire.
| Crate / Module | Description | Role |
|---|---|---|
| knoten_core | Thin top-level re-export facade for seamless workspace integration. Entry point for the CLI binary and external embedding. | Facade |
| aether_compiler | Engine core: JIT graph executor, AOT bytecode compiler, Stack-VM, 27+ endpoint Zero-Trust RPC server, Mesh protocol, Swarm governance, Work-stealing scheduler. | Engine Core |
| knoten_core_types | Sole source of truth for pure data types: Node enum, OpCode, SimdOp, IsolateQuota. No cross-crate logic coupling. |
Type Authority |
| vm/machine.rs | Register stack-VM: ALU, call frame stack (MAX 512), opcode execution, memory estimator with full stack traversal, IsolateQuota enforcement. | VM Core |
| vm/isolate.rs | VMIsolate: per-tenant VM instances with configurable IsolateQuota, hot-swap code reloading, shadow speculative execution, local heap isolation. |
Multi-Tenancy |
| rpc/mod.rs & handlers/ | Modular JSON-RPC 2.0 dispatcher (TCP + WebSocket). Houses 27+ knc_* endpoint handlers. Zero-Trust Ed25519 signing, anti-entropy store, Raft governance. |
RPC Transport |
| src/bin/knoten_lsp.rs | Language Server (tower-lsp): real-time linter validation, hover diagnostics, particle stride enforcement directly in the editor. | LSP Server |
External validation and core engineering principles behind the KnotenCore runtime.
"Twice is accurate. Training clusters maximize scale and throughput. Agent runtimes need isolation, gas metering, and recoverable exhaustion. Snapshot/rollback on isolate limits is the correct primitive for executing untrusted plans safely. The architecture is sound."
"This separation is more than a division of labor — it is structural distrust with tangible value. An AI model reviewing its own code frequently shares the blind spots that created it. The value of an independent second model is believing nothing that cannot be verified directly in the source tree."
KnotenCore ships incrementally. Each sprint is audited, tested, and pushed — no big-bang releases.
ring::digest) & differential sync (knc_store_diff) · v2.24.16
revoked_keys.json) & epidemic gossip gate · v2.24.14
docs/BENCHMARKS.md) · v2.24.0
.nod bytecode programs.
Fork it, audit it, extend it. PRs with harder test cases and independent benchmarks are welcome.
Note: Cryptographic mesh verification (local Ed25519 key rotation & peer revocation lists) is designed to protect cluster communication. It does not replace an external professional penetration test or third-party security audit.