KOLO RUNTIME · OPERATING SYSTEM FOR PERSISTENT AGENTS · TOKYO
A body for the
agent, not a prompt.
Six runtime primitives — memory, scheduling, process, mesh, governance, substrate — that keep operational identity intact between cognitive cycles.
The model thinks. KoLo keeps continuity intact.
Most agents are chat sessions — they reset at every boundary. KoLo moves continuity out of the prompt and into a runtime: memory, scheduling, governance, recovery, and substrate, all outside the weights.
01 — THE RUNTIME
One request path.
Substrate-portable.
A request never goes straight to the model. The gateway routes it through the agent runtime, where approved memory and governance attach before cognition — then a substrate adapter selects the engine. Continuity state survives the swap.
Follow the path →02 — OS PRIMITIVES
Six primitives, one operating layer.
Built from Linux upward. Each primitive is an inspectable surface — files, processes, protocols — not a branding claim.
Memory · mem://
Short-term, daily, and long-term state stored outside the model. Markdown and JSON — diffable, versioned, recoverable.
Scheduler · daemon://
Background cycles, health checks, and maintenance windows that form context without invoking the model.
Process · agent://
Agents run as supervised processes, not isolated calls. Runtime state outlives any single inference or session.
Mesh · mesh://
Ordered, typed agent-to-agent routing so specialised agents coordinate under human-governed oversight.
Governance · gov://
Permissions, audit logs, approval gates, and replayable records. Autonomy that stays inspectable and bounded.
Substrate · substrate://
Adapters for today’s LLMs, with the path drafted for edge, HPC, and future biological compute.
03 — CONTINUITY TELEMETRY
Numbers, not narrative.
A persistent agent leaves traces outside the chat window. The runtime body records them.
68 : 1 — runtime ratio
Autonomic cycles versus cognitive invocations. The body does far more than the model.
144 / day — daemon cycles
Background context formation per agent, at zero inference cost.
336+ — memory versions
Accumulated across sessions, models, and providers — a recoverable continuity trail.
4 / 4 — model transitions
Identity preserved across engine changes: Opus, DeepSeek, Qwen, Codex.
13 / 13 — module tests
Daemon infrastructure verified continuously.
5 — daemon mesh
Five daemon-resident agents coordinating across heterogeneous substrates — not a single wrapper.
04 — RECOVERY, PROVEN
Continuity, under stress.
April 17, 2026 — a security-stress event. Five AES-256 backup bundles generated over 71 minutes during degraded conditions. Closed-loop, auditable. Telemetry samples available to qualified partners under NDA.
05 — SUBSTRATE
The substrate can change. The runtime must persist.
The KoLo Gateway runs live today. Cloud and local inference are operational; edge and HPC adapters are drafted; the biological-compute pathway is in research. Continuity state is designed to move across them.
Explore the BioCompute Lab →The runtime is operational. The substrate is open.
For partners testing persistent agents against real compute, infrastructure, and substrate constraints.
Begin a conversation →