using-compass

name	using-compass
description	Use when a user or another skill directs the agent to use a named compass.

Generated from blueprint.yaml. Do not edit this block by hand.

Instruction Interfaces:

These are LLM-readable instruction surfaces. Read and follow them directly; do not invoke the MCP server for them.

• rutter.interface.dispenser@5 — Construct one VoyageDispenser from self-describing modes, unique run initialization, optionally prefix-filtered ID enumeration, Voyage resolution, and Voyage-or-run release callbacks.

Using Compass

Use compass on <rutter-name>.

Use one invoker-provided authorized VoyageDispenser process binding supplied with the activation request. If it is absent, report a public-interface gap and stop.

First invoke help and follow the returned operating contract. If the activation supplies the advertised mode arguments, invoke modes, then initiate exactly once to create a fresh run, passing the optional run prefix only when supplied. Use only the IDs returned by initiate. If initialization inputs are absent, report a public-interface gap instead of inventing them. Act as the controller: assign exactly one agent to each returned voyage_id, giving it the dispenser binding and its assigned voyage_id. Agents must not share or switch Voyage IDs. Do not start any Voyage agent until every returned ID has an assigned agent. If an independent agent cannot be assigned to every Voyage, report a public-interface gap and stop.

Each Voyage agent invokes status only with its assigned ID. For a ready Message, it performs the instructions and payload, produces a response satisfying the optional response schema, invokes validate, and invokes advance only after validation succeeds. For ready automatic work, it invokes advance without a response. It reads a fresh status after every successful advance and stops on terminal, fault, uncertain, malformed, or unknown status. After reading and retaining a terminal result, it invokes release for its assigned Voyage unless there is an explicit reason to preserve that Voyage's working directory. It reports that reason when it preserves the directory and never releases a ready, faulted, uncertain, malformed, or unknown Voyage. The controller must wait for every Voyage agent to stop before finishing.