Skip to main content

Cross-surface navigation plan (MCP)

The product contract for how an agent moves across Knowledge (Topics), Collections (Records), and Broker (Connections) without listing everything. The rule is retrieve, don’t enumerate. Every step is bounded and names the next bounded step through next_action.

The bounded path

An agent enters at the shallowest known point and stops as soon as it has what it needs.
  1. Every retrieval is bounded and structured; full bodies are opt-in.
  2. next_action names the next bounded call.
  3. A write is reached only after the read path that justifies it.
  4. Search and filters happen server-side; clients never scan a full list.

Where this is encoded

  • MCP tool descriptions and structured outputs.
  • surface-matrix.md.
  • skills/driftless/references/navigation.md and the routing table in skills/driftless/SKILL.md.