EPOCHWORKS
The orchestration engine that runs fleets of AI agents like clockwork — every task on a fixed orbit, every cycle on the record, every outcome reproducible.
hello@epochworks.aiA mechanism, not a mob.
Most agent stacks improvise: agents call agents, order emerges at runtime, and no two runs match. EPOCHWORKS compiles your agent graph into a fixed schedule before anything executes — a gear train, not a group chat.
Deterministic by construction
Every run compiles to a schedule before it executes. Same inputs, same orbit, same result — replay any cycle to the millisecond and get the identical trace.
State you can rewind
Each cycle commits every agent's full state to an append-only ledger. When output drifts, scrub backwards and watch the exact tooth where it slipped.
Autonomy with a governor
Agents act inside declared orbits: explicit tool budgets, spend ceilings, escalation paths. Nothing leaves its track unless a human turns the key.
Five instruments. One movement.
The engine ships as five coupled instruments. Each does one job; the gearing between them is the product.
ORRERYscheduler
Compiles an agent graph into a deterministic execution plan — periods, phases and hand-offs fixed before the first token is spent.
EPHEMERISledger
An append-only record of every state transition in every cycle. Point at any moment of any run and read exactly what each agent knew.
GNOMONdrift monitor
Casts a shadow the moment reality departs from schedule — output drift, cost drift, latency drift — and marks the cycle where it began.
ESCAPEMENTgovernor
Meters model calls into even, budgeted beats. Burst demand queues; spend ceilings hold; the beat never breaks.
MERIDIANhuman gate
Declared checkpoints no agent crosses unattended. Approvals are signed, logged, and become part of the schedule itself — the human hand is a component of the mechanism, not an afterthought bolted to its side.
What we hold the machine to.
No customer logos, no borrowed quotes — EPOCHWORKS is a young instrument, and these are the tolerances we engineer against, stated plainly as targets, not audited claims.
Schedule jitter across a thousand-agent movement — the gap between planned and actual hand-off, measured every cycle.
Replay fidelity. Identical inputs must produce the identical trace, or the cycle is marked defective.
State transitions outside the ledger. Not policy — construction. There is no code path that mutates state without writing first.
If it cannot be replayed, it did not happen.
Autonomy is a budget, not a mood.
The log is the product; the demo is a side effect.
Declare. Compile. Turn.
Declare
Write your orbits in plain manifests: which agents, what period, what budgets, where humans sit.
Compile
ORRERY resolves the graph into a fixed schedule and rejects anything unbounded — cycles, runaway fan-out, undeclared tools — before execution.
Turn
The mechanism runs. EPHEMERIS records, GNOMON watches, ESCAPEMENT meters, MERIDIAN gates. You read the dials.
orbit "nightly-close" { period 24h @ 02:00 UTC agents [ ledger-scan, reconcile, report ] budget 40k tokens per agent per cycle tools { sql: read-only, mail: draft-only } meridian human-sign when drift crosses tolerance replay full-trace, 90d retention }
And what the turn produces: cycle 062184, run on schedule and replayed from the ledger eleven days later. Same inputs, same orbit, same trace — the checksums are the claim.
cycle 062184 · orbit "nightly-close" · run vs replay ledger-scan sha 9f41c2e0 sha 9f41c2e0 = reconcile sha 5b07aa19 sha 5b07aa19 = report sha e33d804c sha e33d804c = meridian signed 02:41Z signed 02:41Z = verdict byte-for-byte — cycle sealed
Set your agents in motion.
We onboard a handful of teams each quarter — few enough to watch every mechanism closely while it finds its beat.