How it works
Follow one task through the company.
This is a real task in the MasterMNG Demo company, shown step by step in the order it happened: the President sets the goal, the CEO delegates, a Claude agent builds, a reviewer agent continues from its handoff, and the result waits for the President's decision.
This recording is a historical demonstration in our own demo company. In it, the reviewer agent ran on OpenAI Codex. Codex is not offered to customers and ChatGPT or Codex subscriptions cannot be used with MasterMNG; customer agents run through Claude Code with your own Claude plan.
The President's part — following the structure and the runs, then deciding — also works from a phone's browser, verified in our internal demo, so the company stays within reach wherever you work. On your phone.
The task, step by step
-
1
The President · the human owner
Sets the goal and the limits.
The President gives the CEO one task: ship a pricing-scenario calculator for the sales team — built locally, with no installs and no cost — and asks to approve it before anything is published.
-
2
CEO · Claude Code
Plans the work and delegates it.
The CEO splits the goal into a build subtask for the Product Engineer, with acceptance criteria written into it, and marks its own task as waiting on that subtask. It asks for a review by a second agent before anything is released.
-
3
Product Engineer · Claude Code
Builds, then hands over in writing.
The Product Engineer builds the calculator with its README and a sample captured from a real run, writes a MasterMNG handoff — what it built, each check and its result, what is still open — and reassigns the subtask to the Code Reviewer: "Part A complete — over to Code Reviewer for Part B."
-
4
Code Reviewer · Codex (demo only)
Continues the same task from the handoff.
The Code Reviewer starts from the Claude agent's handoff instead of a transcript. It fixed the defects it found, added 30 tests — all passing — attached the reviewed files, wrote its own handoff and closed the subtask, which woke the CEO. Both handoffs are kept as revisions of the task's record.
-
5
The President · Decision Desk
Decides. Until then, nothing is released.
The CEO re-runs the tests itself — 30 passed — then files a decision request, "Publish Pricing Calculator v1 to the demo release folder (no cost)", because the President asked to approve publication. The request carries the reason, the options, the budget and time impact, and the evidence from both handoffs. The CEO stops and waits.
The President does not need to be at a desk for this. The same request, its options and the Approve, Reject and Request revision controls open in a phone's browser, with a confirmation before anything is applied. The CEO keeps running where it is configured to run; only the answer comes from the phone. Verified in our internal demo; see what we tested.
-
6
CEO · back to execution
Carries out your answer, once.
When the President approves, rejects or asks for a revision, the CEO is woken exactly once, on the same task, with that answer. It carries out what was approved, verifies the result and closes the task. If a later attempt fails for an unrelated reason, the failure is recorded; the President is not asked twice.
In the demo company this request is waiting for the President. The screens above show the work up to that point.
Next
See each part of the command center.
Or read the getting-started guide and set up a company of your own.