{}
Ring API (read-only tap)
/api/ring returns the live topology — nodes,
next_hop edges, accents. The same data this page renders from.
MkrOps · Engine & Ops
mkrops.io is the operational surface — the bridge mesh where work propagates through the engine. Five nodes, one direction, one open broadcast tail. This is the engine's actual shape, served straight from the ring.
Surface map
One engine port. Three public faces as protocol-over-port. A small set of read-only taps. The ports and endpoints below are real topology — only the metrics are sampled.
The mesh
Work enters at the desk, is staged across the bridge, gets pulled by agents, and loops
home through the portal — which closes the hoop and leaves an open broadcast tail.
Five nodes, propagating in one direction. next_hop is data, not code:
add a node and the lap grows. topology is public in ring.json
Front / commerce intake — the open door.
front.open.intake|in
Bridge ingress — work is staged into the engine.
office.stage.work|thru
Bifrost span — the engine throughput; the ticker lives here.
bridge.span.throughput|thru
Factory floor — agents pull tickets here.
agents.pull.ticket|in
The hoop closes here — loops home to desk and leaves an open broadcast tail.
portal.close.hoop|out
portal → desk — the lap closes back to the open door ·
center [0.0.0.0] · hollow genesis = sha256("")
Engine status sample feed
Numbers are illustrative — the engine isn’t necessarily running during this preview.
Tooling
Everything you tap is read straight from the ring vocabulary — no shadow API, no invented surface. Stage work in, watch it propagate, read the record back out.
/api/ring returns the live topology — nodes,
next_hop edges, accents. The same data this page renders from.
Every lap leaves an entry, chained to the last. Genesis is the hollow hash — sha256 of empty — the hoop both ends close back to.
The office node stages work into the engine. Once staged, it propagates one-way across the bridge span without you steering each hop.
/health reports per-node and whole-ring liveness, so
you know which segment of the lap is carrying and which is quiet.
Agents at the factory floor pull tickets through the Claude pipeline — the .ai surface where work actually gets made.
page ≡ container ≡ datastore ≡ service ≡ protocol-over-port. One addressing model; the surface you hit decides the protocol.
Read the ring, watch the lap, pull the ledger. The topology is public — start reading.