Read the context packet for a view (§1.4): the selection's resolved referents and current params, the recent history, the conversation labels, the project state, the budget left tonight, and the vocabulary and its gaps. Pass the node ids you are looking at; omit them for the world's own situation.

The closed, typed vocabulary: words with their kinds, owners, statuses, param schemas and taste notes. Filter by status to see the coming-soon edges — the gaps that only a work order can close.

The night's plan and its price: the slated tasks with their asks (the cost model's p50, or the filer's override), the bar (the night's rails), the owner's two lines — what tonight costs and whether it fits — and the budget left if a night is running.

Change the world through the typed vocabulary, sealing the prediction FIRST (§5.1: the seal is committed before the render exists). The word's param schema is the contract; anything outside it is refused at the door and the refusal is honest. The render that tests the prediction is requested separately (request_render), so the bet stays sealed before its test exists.

Request a render or preview of entries at a rung of the ladder (1 fast layout · 2 mid with lighting and materials · 3 full). The request is queued at the core's door priced by the measured cost model (kind rung.N); the engine that renders it is the recipe half's seat, so until it lands the queue row is the honest state. Price a sealed prediction against the SAME rung and seed you render.

File a work order from a terse request plus the context packet: the core captures the packet, resolves the referents through the node registry, and compiles either a draft (with the one-line confirmation and BOTH price lines) or — when two referent sets are both plausible — a one-tap question. It never guesses; answer the question with answer_question. Fill intent.spec_sentence (≤ 25 words), intent.goal, intent.acceptance (≥ 1 machine-checkable check) and intent.estimate {build_verify, generate_test} to shape the compile.

Answer a draft work order's confirmation: go (queue it), no (cancel), or edit (cancel and refile with amendments). This is the owner's one word; the call is idempotent by key. Pass the idem_key again if a retry must not double-file.

Answer a parked question (the never-guess rule: when the compile found two plausible referent sets it asked, and the answer unblocks the work order). The options are on the question; answer with one of them, in the owner's words.

Propose to the night's slate (kind plan.intention): a plan you believe the night should run — read world://context first and aim the proposal at a real gap. It is priced by the cost model like everything else, but the band is the proposal's own footprint: a slate row and the owner's decision on it (zero GPU; the attention estimate, marked [e]). It prices the proposal, not the work it may seed — that work is priced by its own kind when the night runs it. The owner reads the slate before starting the night; starting it is their door, not yours.

Queue a generative batch (genbatch): a night of props made by the local image model + TRELLIS.2, measured, judged and recorded as assets with provenance and licence. The kind prices it from the measured cost model — prop.512 or prop.1024 per variant; count scales the ask (the p50) and the rail (the p95). The requests themselves ride the intention (what to make, how many seeds); the genbatch seat consumes the queue.

Subscribe to world.dirty: what changed in the world and when. Returns the cursor {branch, head, seq} and the dirty events since since_seq (rewind is free — the feed is the log). Clients that hold a subscription stream receive world://dirty resource-updated notifications the moment the recipe moves; this tool is the polling form for clients that cannot.