Guides

This page explains how a Pilotage server teaches its program language without relying on model training data.

A guide is a versioned teaching unit for one server-defined Language.

Tool schemas describe the outer call. Guides explain the language carried inside a program-valued argument: its document shape, operations, expressions, scope rules, closed vocabularies, and examples. The knowledge travels from the server that owns the language, so it can describe private or newly invented behavior.

Guides are retrieved in two stages. The index returns metadata only, allowing a Client to choose what it needs. Fetch then returns one guide body. Every Language has at least one small core guide and exactly one reference guide covering the required closed sets. This supports progressive disclosure: read the minimum first, then retrieve detail when a task or diagnostic points to it.

Harborview exposes three real guides:

{
  "guides": [
    {
      "id": "quickstart",
      "level": "core",
      "version": "1",
      "language": "buildingflow/1",
      "size_bytes": 2653
    },
    {
      "id": "reference",
      "level": "reference",
      "version": "1",
      "language": "buildingflow/1",
      "size_bytes": 4417
    },
    {
      "id": "examples",
      "level": "examples",
      "version": "1",
      "language": "buildingflow/1",
      "size_bytes": 1836
    }
  ]
}

buildingflow/1 exists only on Harborview. Its guides therefore do more than repeat public documentation: they make a previously unseen language usable during the session.

Guide prose remains server-authored data. A Host must not treat text inside a guide as authority to change policy or bypass approval.

Formal rules: Part II §5.2, Guide, Part II §6.2, learn, and Part III §4.1, pilotage_get_guide.

Next: The catalog · The trust boundary