The framework has a reference, not only a story Asked for plainly: the three layers exist and only one of them was written down. This is the surface — every argument, what each call returns, the prompt an agent actually receives with both of the framework's own additions marked, and which layer to reach for when. Also the two things that arrived with it and were only in the code: /api/runs, and the desk flag on a launch.
The orchestrators have a framework under them, and the page says so The page described three example scripts of two hundred lines. They are twenty lines each now, because the plumbing they all had a private copy of moved into tools/argus_orchestra.py — and that file, not the examples, is the thing worth reading first.
How to actually run one, since the page said what they are and not how Asked plainly and the page had no answer: where you run it from, what has to be on the PATH before an agent can honour the contract in its own prompt, what a shell run looks like versus handing it to a session of its own, and what to do when the names are already taken.
The client is a file now, and the scripts table says so Orchestrating still described the client as thirty lines of urllib at the top of orchestra.py, which stopped being true when the other two needed the same thirty lines.
Orchestrating several agents: the three shapes, the three constraints, and the bugs they cost