KoLo · HPC & DEEP-COMPUTE · TOKYO
The runtime your cluster is missing.
HPC has the compute. The substrate is here. None of it has continuity. KoLo lives between the model and the metal.
01 — THE THESIS
Substrate has outrun the software.
Neuromorphic chips ship. Wetware platforms run live experiments. Clusters saturate with frontier inference. Every one assumes an agent runtime that preserves memory, identity, and behaviour when the model underneath changes.
KoLo is that runtime. Built on silicon, designed for the day the substrate beneath it is no longer silicon.
02 — SUBSTRATE-PORTABLE
One continuity,
any substrate.
Persistent memory, closed-loop autonomic scheduling, peer mesh, and a substrate adapter — open, observable, recoverable. Adopt it now and you will not rewrite your agent stack three years from now.
03 — THE ARCHITECTURE
Four layers. One continuity stack.
Memory substrate
Short-term, daily, long-term, governance spine. Markdown + JSON on disk — diffable, replayable, recoverable across substrate change.
Closed-loop daemon
Circadian scheduler, circuit breakers, novelty router, memory dedup. The loop shape biological substrates need to be programmable. 13 / 13 tests passing.
Agent mesh topology
Type-safe, ordered, transactional A2A messaging. No hierarchy — each peer spawns its own sub-agents. Maps cleanly to MPI-style cluster communication.
Substrate abstraction
One API across LLM providers, edge accelerators, and neural substrates. Reference adapters shipped; the bio adapter awaits a hardware partner.
04 — WHAT WE MEASURE
Engineering numbers, not narrative.
Over 99% of the operational body runs without model cognition — a deterministic daemon body pulsing continuously at zero inference cost. Four frontier-model transitions completed with continuity preserved: Opus → DeepSeek V4 → Qwen → Codex. 336+ memory versions, none lost.
April 17, 2026: five AES-256 backup bundles written autonomously in 71 minutes during a malware incident — no human prompt, no model inference.
05 — DEPLOYMENT
Four ways KoLo lives on your hardware.
On-prem HPC cluster
Gateway as a long-running service, daemons as per-agent processes, memory on a shared filesystem, inference dispatched to cluster-reachable endpoints.
Air-gapped sovereign
Same runtime, local-only inference (vLLM, Ollama, in-cluster TGI). No outbound traffic. Memory and audit stay on customer soil.
Hybrid edge + cloud
Lightweight daemons at the edge — Jetson, neuromorphic accelerator, SBC — with cloud failover. Identity stays with the node; inference roams.
Federated mesh across labs
Each lab runs its own KoLo and federates agents over A2A. Joint experiments without joint data exposure.
06 — WHO WE BUILD WITH
Three labs.
One runtime layer.
Biological-compute platforms running living neurons on multi-electrode substrates. Neuromorphic vendors with spiking, low-power inference. HPC operators and national labs producing reproducible cross-substrate benchmarks.
HPC & BioCompute Lab →07 — THE ENGAGEMENT
From kick-the-tires to joint paper.
Four phases, each with an explicit deliverable, each exit-able without lock-in.
Phase 0 · Pilot
Gateway and a single daemon on a partner substrate or endpoint. Continuity benchmark run; telemetry shared.
Phase 1 · Adapter
Substrate adapter against partner hardware. Closed-loop scheduling and recoverable state confirmed; a silicon-to-substrate transition test.
Phase 2 · Mesh
Multi-agent peer mesh across partner substrate and silicon. Federated identity across nodes; a long-horizon autonomy run.
Phase 3 · Paper
Joint methodology paper — reproducible benchmarks, adapter-spec contribution, governance appendix. Peer-review-targeted.
継
Bring the substrate. We bring the runtime.
Engineered, tested, and waiting for the first non-silicon substrate underneath it.
Discuss a lab pilot →