The Landing climbs from the toolbox to the colleague

[davideimola]

Argus derives one of two shapes from a single fact — whether an LLM provider is configured — and the Landing was written when only one of them existed. It opened at its maximum, Argus arguing back on a pull request, and then descended into configuration; the third story beat closed on "A colleague, not a toolbox" while Toolbox was a shipped shape.

The page ascends

The spine is now: hero, the floor in the reader's own editor, the same floor across a team, the turn, the three story beats, the consultation, Trust.

It starts where a reader can start today, with Argus serving its scanners and what the organization knows to the AI tool they already pay for. It adds the model that makes it a colleague. Only then does it tell the pull-request story, which now reads as what the model unlocked. Trust closes, so the boundaries land after the climb instead of interrupting it.

The hero deliberately does not carry the first step. A reader at the top has not yet learned that Argus uses a model at all, so "no model required" up there answers an objection nobody has raised, and an opening that sells the tool the reader drives sells the product below its own ceiling. The zero-cost first step is not lost by that: it lands thirty seconds in, and in the meta description that link previews show. ADR 0013 records the order and the exception.

The words are the Guide's

Toolbox and Colleague are adopted rather than invented, and agentless is refused however well it would have fitted: in application security it already means "nothing installed on the host", and a toolbox is a daemon on the machine the code is on. ADR 0012 records both, and CONTEXT.md gains the three terms along with the words each one is not.

Two places the page was about to stop short of the Guide

• The shared instance shares what Argus knows, not where it reads. Scanning stays on the host Argus runs on, and the page now says so.
• The consultation panel moved out of the toolbox section it used to share, because consult is served by a colleague only. A toolbox section was demonstrating the one thing that shape cannot do.

What holds it

src/landing/bands.ts derives the raised band from the section sequence instead of deciding it per section, which survives exactly until the page is reordered. The page declares its order once and every section asks; asking about a section the order does not name throws, so a stale id fails the build rather than silently shifting the rhythm of everything under it.

Four guards in landing.test.ts, each verified by mutation:

• the refused words are read out of CONTEXT.md, so arming the glossary arms the test;
• the page has to name both shapes — the half that went wrong quietly while the refusal passed;
• no snake_case name may appear anywhere in the copy, because MCP tool names, config keys and environment variables are all snake_case and all Inventories the Guide owns;
• every id the order declares has to be rendered.

astro check clean, 150 tests, build clean with 114 internal links resolving.