An agent can ask you a question
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.
Document what the last few days added, and make every file mention a link The wiki names files constantly and none of them were clickable: it is a separate repository, so a relative path never reaches the code and it has to be an absolute URL. Eleven of them now are. And the content had fallen behind the app: the workspace on the machine and what that unlocks, the Python client and why it is one file rather than a package, the to-do list, fetching a link into a folder (with the pasted curl), the caption under a document, sending a window behind, and the brakes — which the page still described as six a minute, from before the fan-out of four referees and an editor proved that wrong.
An agent driving Argus, and Swagger on your own machine