The crew and the Analyzer

The CREW pull

Say open the crew or click CREW on the sill. Every body in this world stands on one page, both sides of each: what it served (side A, direct inference from the chat) and the job it runs (side B, the duties on its clock). When the Rust kernel seats the bodies itself, each card says where its process stands — alive, restarting, PARKED or refused. The crew’s own firmware agent joins the chat and answers about the cards.

A card reads: the body’s name and nature · its kind (resident or firmware) and self (DID) · its lives · the policy version it wears · its capabilities · its mind (which stall, and why — or the honest word that no mind stands) · its placement (which cell, which metal) · its spend and its fuel · every schedule it runs, marked editable or kernel-required.

Say	What happens
what services are here? · show the tools · show the LLMs	The shelf: every tool, MCP server, store, source and mind on one ladder — registered → versioned → healthy or unhealthy → retired.
toolkeeper, add the MCP server at ‹command or URL›	The server and its tools land on the shelf as identities; its secrets by env name only, never a value.
retire the weather tool · restore the weather tool	Retire holds at the interlock; restore is a new fact. Retired is dormancy, never deletion.
stablekeeper, add the LLM ollama gemma3:270m as gemma	A mind wherever it lives — anthropic · openrouter · ollama · openai · compatible — becomes a stall in the Stable and an entry in the gateway; held for your yes.
assign librarian to gemma · assign librarian to gemma for fast work · unassign librarian	Which mind a body uses, for all its work or one class (fast · standard · deep); the card says LLM: … and why.
librarian’s fuel · refill librarian by $2	A body’s allowance for this window and what it has spent; a refill holds at the interlock — real spending.
schedule an ask for librarian… (on its card)	A standing duty on the clock, shown on the card’s job side; rest it stops it. Kernel-required duties are visible, never editable.
restart the echo body	A parked or refused body tried again on your word — the same self.

The shelf and the Stable, beneath the bodies

The shelf is one register for every service the kernel governs: the nine built-in tools, any MCP server you add (each of its tools a self on the ladder; a changed list versions it, a vanished tool goes unhealthy “gone from the server’s list”), the ground and the Record as stores, and every mind. Each has its own DID, a manifest hash, a placement, and a health probed on the toolkeeper’s cadence. Three unhealthy probes in a row and the keeper proposes a retire; it never retires alone.

The Stable is the minds’ side of that shelf: each a stall with a pinned deal (provider, model, price per million tokens, context, modalities, class) and an entry in the gateway. The stablekeeper pings every mind on its cadence, watches price drift (a drifted price is unhealthy and proposes a re-pin) and announced retirements (a swap proposed thirty days out), and notices a drained body (a refill proposed).

The ANALYZER hatch

Lift the floor — click ANALYZER on the sill — and everything born in the chat is there, grouped by origin: intentions, the objectives under them, their thoughts, actions and observations, in flight and done, read from the ground. Nothing sent to it → all active and completed intentions and objectives, yours and the kernel’s. An origin sent from the chat → that origin’s tree. It is a projection: with ten thousand markers on the ground it paints in a few milliseconds and asks no body anything.

Every row is a door. Click an objective’s row and the chat takes it as its focus; follow up on this by … files a child under it. The MARKERS view lives here too — lineage is history, and the monitor stays now.

Say	What happens
(click a row)	Its tree in words; an objective’s row puts the chat in focus on it.
stop the kernel’s Resiliency intention	A grave act: your code, then a declared master’s click; the intention rests, recorded, never deleted.
restart intention ‘‹its words›’	The reverse, through the same ladder; it stands again.

The five standing intentions

The kernel declares its own intentions at boot, with no end and each with its stop: Business · Security · Resiliency · Compliance · Cost. Resiliency is at work in every world today — keep this world resilient: when a watch goes red, get it green — with the planner as its planner and the librarian as its runner; a red watch is its observation, a lever its action. Saying those same words yourself is refused with the reason: an intention with these words already stands — the kernel’s is at work; stop it first, or say what is different. The other four are declared and wait for the interests and runners that make them act.

Markers

Every fact carries a marker: its typed reason and its parent. The kernel seeds the structural kinds — objective, intention, thought, action, observation — and two more stand on a fresh world: improvement (quality) and watch-red (resiliency). A body sets a marker on whatever it is executing through the mark tool; a template declares the kinds it is interested in, and the kernel dispatches it an ask whenever such a marker lands, with that marker as the parent. The critic is interested in improvement; Resiliency in watch-red. The chain says who; the marker says why; both are on every envelope and never conflated.