Autonomous engineering runtime

The runtime that owns the loop.

Zerg is the agent engine that turns specs, tests, manifests, modules, files, tools, and live runtime signals into a continuous engineering loop.

Manifest-driven executionSpec and test loopsModule probesSnapshots and traces

Zerg surface

live

map

repos, APIs, databases, docs, hardware surfaces, and operator rules before acting

act

generate code, configs, tests, harnesses, migrations, and operational fixes

prove

use tests, probes, traces, and real signals as feedback for the next step

watch

keep running after delivery so drift becomes queued work instead of hidden risk

What it owns

Built around the system, not the demo.

Evidence

Mixin-based agent core with pluggable backends, environments, workflows, memory, traces, and control state.

Evidence

YAML manifests compile specs, tests, stages, references, modules, and workflows into executable agent behavior.

Evidence

Module runners watch external systems on their own cadence and feed structured events back to the agent.

Operating model

01
Models repos, APIs, databases, hardware surfaces, docs, and operational constraints before acting.
02
Uses tests, probes, and runtime feedback as first-class inputs to the next generation step.
03
Keeps watching for drift so production change becomes queued work instead of hidden risk.

Zerg