Graph first · harness second · evidence third

One dashboard for AI workflow readiness.

Starboard shows which workflows have graph, harness, and evidence coverage, which are blocked, and what compliance should inspect next. It reads Planisphere records; it does not invent scores or replace approval.

Ship’s bell strip

Hear the fleet before you steer it.

The helm needs bells, not another feed: event, readout, analysis, path to proof.

bell 01 at sea

Law-board

MECHPrompt edge captured · trace path selected.

ANALYSISLegal workflow has evidence internal or external compliance can inspect.

bell 02 at sea

Corpus Library

MECHRegistry read · bell events visible.

ANALYSISFleet status comes from sealed bundles, not a new measurement.

bell 03 at sea

War-board

MECHDefense vessel reports readiness.

ANALYSISThe next decision is steering, not re-running the audit.

bell 04 drydock

Next-board

MECHConfig registered · no bundle loaded.

ANALYSISAbsence stays visible; drydock is not hidden.

01 ·

The helm above the boards.

One console · every vertical a vessel · steer what is ready port beat-01 · the I/O frame

A Board shows one vertical. Starboard shows the line: law, defense, education, medicine, and the corpus library each as a vessel with its own evidence status. Operators see what is crewed, what is blocked, and what should move to compliance next.

Starboard does not re-measure. Astrolabe takes the reading, Backstaff seals the record, and Starboard reads those sealed grade-vectors. A new vessel appears when its config registers in the kernel; the helm is generated from the registry, not rewritten by hand.

One helm: see every vertical’s standing, steer what is ready, crew what is next.
02 ·

A vessel is a vertical’s standing.

Crewed or in drydock · readiness = share of PASS cells port beat-02 · the two faces

A vessel is one SKU’s evidence standing. It is crewed when an attested bundle is loaded; readiness is the share of PASS cells across that vertical. With no bundle, it stays in drydock at zero instead of disappearing.

Each standing points to its attestation root. Change the bundle and readiness moves with it.

The helm
one hub · a line of vessels

Brass tips mark vessels. The hub reads their sealed standing and steers the next compliance action.

Stand War-board, School-board, and Law-board side by side; Starboard reads one line.
03 ·

The fleet today.

Five registered vessels · law, defense, education, medicine, on corpus library port beat-06 · the fleet inbound · the boards outbound

The line currently names five vessels: War-board, School-board, Law-board, Medicine-board, and the base Corpus Library.

The catalog is open-ended. Registered verticals appear automatically; unbundled ones stay in drydock.
04 ·

The console.

Every vessel · its readiness bar · the whole line in one number backstaff beat-06 · the canonical list grows on the body

This is the helm at a glance: status, fleet size, readiness bar, and one fleet-wide line.

  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 Library 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. Rows fill from attested bundles; no bundle reads drydock at zero.

Vessels sort by service state, readiness, then SKU: ready first, blocked last, nothing hidden.

Fleet readiness is one PASS-cell ratio across crewed vessels, recovered from sealed bundles. Nothing here is re-measured.

05 ·

Next step.

Open a vessel · or register one port beat-09 · the close

Open an existing vessel, or bring a new workflow to the same helm. The next step is a scoped compliance evidence pass.

——— the Starboard · one helm, a line of vessels · steer what is ready, crew what is next ———