One helm, a line of vessels.
Steer what is ready, crew what is next.

A Board renders one fleet — one vertical’s grid of adapters and the grades they earned. But Planisphere does not run one fleet; it runs a line of vessels, each vertical a SKU with its own audience and its own compliance waters — law, defense, education, medicine, all riding on the base corpus. Mission Starboard is the helm above the Boards: the single console where an operator sees every vessel’s readiness at once — which are crewed and at sea, which sit in drydock — and steers which to put to sea next.

The Starboard re-measures nothing and re-grades nothing. The Astrolabe takes the reading; the Backstaff attests it; the Starboard reads the whole line’s standing from the sealed bundles the spine already produced, and steers. Each vessel’s readiness is recovered through the same Board path the Boards use — the bundle’s sealed grade-vectors are the source of truth, never a fresh measurement.

The catalog of vessels is not authored on this page. It is exactly the verticals registered in the kernel: a new vessel appears on the helm the moment its config registers — no Starboard edit, no Planisphere release. The helm is emergent from the registry, honest by construction. It pairs against the Port — the inbound, content-agnostic boundary where any hosted AI tool docks — but its own work is outbound and singular: read the fleet, steer the fleet.

A vessel is one SKU’s standing in the fleet. It is crewed — put in service — when an attested bundle is loaded onto it: the Starboard recovers that vertical’s grades through the canonical Board path and summarizes its readiness as the share of PASS cells across the whole vertical. A vessel with no bundle yet is honestly in drydock — listed, never hidden, with zero readiness. Nothing is re-measured at the helm; the sealed grade-vectors are the source of truth.

Each crewed vessel’s standing is tied to the exact attestation root that produced it — change the bundle and the readiness moves with it. The standing is not an assertion; it is a pointer back into the hash-chain the Backstaff sealed.

The line carries five registered vessels. Three carry their own mark below — the War-board (defense), the School-board (education), and the Law-board. The fourth regulated vessel is the Medicine-board, live at /medicine against its contracts (HHS §1557, FDA PCCP/SaMD, HIPAA). All four ride atop the base Corpus vessel at the hub.

This is the helm at a glance — the view planisphere.starboard.render prints. Every vessel shows its status, its fleet size, and a readiness bar; one line at the top carries the whole fleet’s readiness.

  THE STARBOARD  ·  5 vessels  ·  fleet readiness  84.7%

  vessel         sku        status     fleet  readiness
  Law-board      law        at sea        14  █████████· 91.4%
  War-board      defense    at sea        11  █████████· 88.2%
  Corpus         corpus     at sea        21  ████████·· 83.1%
  School-board   education  at sea         9  ████████·· 81.0%
  Medicine-board medicine   at sea         8  ████████·· 80.5%

  one helm, a line of vessels — steer what is ready, crew what is next.

Illustrative. Each row fills from that vessel’s live attested bundle; a vessel with no bundle reads drydock at zero.

Vessels sort the way an operator steers: in service first, then by descending readiness, then by SKU — what is ready, what is closest, what is next. A vessel in drydock falls to the bottom, listed honestly at zero rather than hidden.

Fleet readiness is the share of PASS cells across every crewed vessel — the whole line’s standing in one number, zero if nothing is at sea. It is not an average of averages; it is one ratio over the live grades, recovered from the sealed bundles. Nothing here is re-measured.

If your domain is one of the vessels already at sea — law, defense, education, medicine — open it directly. If your domain is something else entirely, open a procurement channel: a new vessel registers onto the same helm without a Planisphere release.