DESIGN

star-trek — product design

The Star Trek Web Dashboard: the Field Marshal and Grand Admiral surfaces for the Expansion Capture & Intelligence Platform. A standalone product, not an Atlas flow — same tier as Atlas, Caesar, and Polaris in the site’s catalog, with its own account system and its own real Landing + Login.

Rationale

Field Marshals and Grand Admirals may not be full MocX/Rechaj staff — the same reason the Survey Agent mobile app (rechaj-star-trek-app) isn’t bolted onto the existing Agent App. They don’t get Atlas SSO, so this can’t be products/atlas/flows/* no matter how much its shell resembles one. It still builds on the same Polaris/Caesar web canon (sidebar/topbar/.pg-wrap, .tbl, .pstat, .dlg, .badge, toast) as every other web product — only the account boundary differs, not the design system.

Personas

Persona	What they do
Field Marshal	Creates and works expansion areas, staffs them with Survey Agents, runs the continuous image-cleanup queue. See flows/field-marshal/.
Grand Admiral	Creates Field Marshal accounts, does the final 100-image spot-check + area approval, blocks Agents/Field Marshals. See flows/grand-admiral/.

Inherits from global DESIGN.md

• Web shell, .dlg, .tbl, .pstat, .badge, .fld — same canon as every Atlas/Caesar/Polaris page.
• Login — this product does NOT use the canonical Atlas composed scene. A recorded, deliberate exception to the Login hard rule, taken because Star Trek is a standalone product tier with its own account system rather than an Atlas flow, and its sign-in is a real wall the reviewer meets rather than dead weight. Two departures, both intentional:
  1. Split layout, not the centred composed scene. Form on --surface at the left, four capability cards on --grey1 at the right. No .login-scene, .login-halo, .login-float, .login-pool or .login-card. The right panel carries generated contour lines (.lg-contour) rather than a tiled pattern, so nothing repeats.
  2. Filled containerless objects for the capability icons (.lg-ob), against the global outline-icon rule. These are illustrative objects on a marketing panel, not interface icons. Scoped strictly: every interface icon in both flows stays outline in a circular .pstat-ic container, including the dashboard KPIs. Both flows share this login byte-for-byte apart from the prefilled email. If you are about to “restore” the composed scene here, this is the note saying not to.
• 3+ filters collapse behind one .btn-sec + .badge count + .dlg (Reset/Apply), with the active-filter summary riding the .pg-title-row — never a separate block that shifts the content below it.

Screens

See flows/ for the canonical interactive HTML flows.

Prototypes / precedent reused

• Vehicle Gallery card (.gal-grid/.gal-card) reused verbatim from products/atlas/flows/expansion-intelligence/index.html, the existing read-only Star Trek Console’s own gallery — including its within/outside-radius badge convention.