You wouldn't trust a deploy pipeline you couldn't inspect. Same rule here. This is the full path of a single run, from the event that wakes it to the deploy that closes the loop. It also shows what holds at every station. Wire it once. The loop runs for new features and last night's dependency rot.
timestamps from a representative nightly-deps run · your repo · your gates
T+00:00.0 · STATION 00
An issue opens. CI fails. A schedule fires. Someone asks in Slack. A standing assignment comes due. Mogplex catches the event, dedupes it, and assembles the context that matters: the repo, the thread, the logs, the diff.
▪ held — one event, one run. Nothing polls your repo. Nothing runs on your machines.
T+00:00.8 · STATION 01
The pipeline you wired decides everything up front: which repo, which harness (Mogplex native, Claude Code, or Codex), what context it gets, and which gates its output must pass. The system records that decision before any work starts.
▪ held — every run traces back to the exact event that caused it.
T+00:04.2 · STATION 02
A fresh microVM boots with a clone of your repo. Nothing is shared between runs. You do not need to connect a cloud account before your first run. Sandbox minutes bill on the meter, and a $10 top-up buys 2,000 minutes.
▪ held — per-run isolation. Your code never executes on shared infrastructure you can't see.
T+00:06.5 · STATION 03
The agent writes code, runs your tests, and calls your MCP tools. It iterates until the tests pass or its budget stops it. Mogplex gives you model access. The system meters and logs every model call and tool call.
▪ held — open any live run call-by-call. Approve the next tool call, redirect the plan, or kill it.
T+04:12.9 · STATION 04
Output leaves the sandbox only one way: as a PR, a check run, or a merge that passed the gates you configured. Branch protections always rule. Mogplex cannot bypass required reviews, required checks, or protected branches.
▪ held — nothing ships that your rules wouldn't let a human ship.
T+04:40.1 · STATION 05
When the change deploys, the deploy points back to the run. The run points back to the event. The audit trail shows what asked for the work, what did it, what it cost, and who approved it. Then the pipeline loops back to the trigger. The same system that built the change now maintains it.
▪ held — “who did this and why” always has an answer.
HARNESSES
The native Mogplex agent, Claude Code, and Codex. Pick the harness and model per pipeline. Every call is visible call-by-call.
SANDBOX
Every run gets a fresh, isolated microVM. Nothing is shared between runs.
GATES
Branch protections, required checks, and required reviews always win. Autonomy is a dial you set per pipeline.
SOURCE
The platform is Apache-2.0. Read what authenticates against your repos before you run it.
RECONCILED. the deploy points back at the run ↺
SHEET 03 — END
no monthly fee on payg. no sales call, no hidden rates.