The substrate · Not a download

Supervision and uptime,
beneath the fleet.

NockOS is the internal operating layer beneath the Nock fleet: process supervision, heartbeats, and uptime tracking. One of many runtimes Nock Command coordinates, not the only one.

Animated demo: a nockos fleet status console listing five agents with heartbeats and uptimes, ending with a fleet uptime of 99.98 percent.

What it runs

Keep agents
alive and honest.

NockOS supervises agent processes on the machine that runs the fleet. No daemon spread, no cloud.

Supervision 01 · proc

Agents that crash are restarted in under a second. Crash loops are caught and reported, not hidden.

[supervise]
restart  = "always"
backoff  = "1s"
Heartbeats 02 · beat

Every agent emits a heartbeat. Miss two and NockOS flags it: you know before the work stalls.

[heartbeat]
interval = "10s"
miss_max = 2
Uptime 03 · log

Per-agent and fleet-wide uptime, logged locally. Pipe it into Nock Command for one-screen visibility.

[uptime]
track  = "per-agent"
export = "command"
How it works

Three primitives.
Every agent accountable.

NockOS sits beneath the fleet. Three primitives (supervision, heartbeats, uptime) keep every agent accountable.

01

Agents register

Each agent registers its name and start command. One line per agent.

02

NockOS supervises them

Crashes restart in under a second. Crash loops are caught and reported, not hidden.

03

Heartbeats are checked

Every agent emits a heartbeat. Miss two and NockOS flags it before the work stalls.

04

Status flows to Command

Fleet status streams to Nock Command for one-screen visibility across every agent.

Under the hood

NockOS is the substrate. The products above it are what you work with.

# NockOS keeps the fleet alive
[ok] runtime online
[ok] 14 agents supervised
[ok] fleet uptime 99.98%
[ok] status → Nock Command
In production

The uptime ledger:
15 sprints, 14 agents.

NockOS has kept the founder's 14-agent fleet alive across 15 sprints of continuous work.

99.98%
fleet uptime
14
agents supervised
< 1 s
restart time
0
cloud dependencies

The layer that
keeps agents
accountable.

The stack

The rest of the fleet.

NockOS is one runtime. The fence, the memory, the playbook, and the dashboard run above it.