Say that the reference is checked, and add the script that checks it The reason to trust a hand-written reference is that something fails when it drifts. Now something does, so the page says so.
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.
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.
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.
Orchestrating several agents: the three shapes, the three constraints, and the bugs they cost
An agent driving Argus, and Swagger on your own machine
Diagrams in a document, and the two vendored libraries the list was missing
The code viewer, and choosing one by extension Also: highlight.js in the vendored list, BSD-3-Clause, with the note that it is imported only when a file of code is opened.
The README's thousand lines live here now Everything it does, the API and Development came out of the repository's README, which had grown to 948 lines — so the answer to 'what is this' arrived about nine hundred lines before anyone could reach it. The catalogue is worth keeping and worth searching; it just is not what somebody wants in the first ten seconds. Internal anchors were rewritten to point at pages, and the screenshots at the repository's raw files, so nothing in the move ends up pointing at itself.