Four operations tools. One shared interface language.

FishHouse began with a cold-chain question: how can someone understand both where the stock is and whether it can move? A campus view supplies the first answer. Lot detail, quality conditions and shipment milestones supply the second. Keeping them connected is the product-design problem.

I organized the workspace around a selected terminal, then kept stock, dock and fleet information in persistent screen-space panels. Outdoor and indoor views change the physical context without asking the user to relearn the controls. The example shown here is Riverside Hub, one of five fictional terminals.

The reusable work sits beneath the screenshots: a Suite library used by FishHouse, Cube Storage, Staffing and Wind Farm. The live catalog currently lists 67 registered components and lets a reviewer filter by application, layer or name. Component usage is derived from source, so the catalog shows where a pattern actually appears.

Shared tokens own color, typography, sizing, radii, elevation and stacking. Urbanist is the common typeface. FishHouse orange, Cube Storage red, Staffing pink and Wind Farm cyan provide identity through application accents; navigation, focus, field behavior and status semantics remain shared.

The library separates chrome, actions, forms, surfaces, data, primitives, overlays and scene rails. Topbars and search establish context. Badges and meters explain state. Tabs, filters and chart surfaces support detail. This makes consistency a reusable implementation decision, rather than a visual checklist repeated in four files.

Staffing demonstrates the system outside warehouse logistics. Its capacity dashboard compares demand and available people across a selected planning horizon. Filters, horizon controls, KPI cards and charts preserve the same control hierarchy used around the 3D scenes.

This is why I separated reusable interface behavior from domain logic. A workforce planner needs capacity and assignment language; a warehouse operator needs lots and dock status. They can share an interaction grammar without sharing a data model. The visible counts and forecasts are demo records, not business results.

Wind Farm takes the shared foundations into asset inspection. The browser twin contains turbines, cables and substation context; its AR companion presents the selected asset with diagnostics and a phone handoff. The desktop view remains a rotatable 3D preview.

The companion explains the route into iPhone AR Quick Look or Android Chrome WebXR. The screenshot records the browser preview and handoff, not a claim that real-world tracking was tested here. Keeping that distinction explicit helps a reviewer understand what is built and which device checks remain.

A lot can be present but unavailable for dispatch. In FishHouse, local quality holds and simulated chilled-temperature excursions affect eligibility. Frozen cargo is not indiscriminately blocked by a chilled-zone issue. Shipment transitions also update represented vehicle movement and allocated quantities.

The optional browser tools have a smaller remit: read the selected warehouse state and inspect an object from a known ID list. They are feature-detected and schema constrained. This is an agent integration surface, while the operating simulation continues to work through ordinary UI. It is not an autonomous ERP workflow.

The shared-system handoff names the source owner for each token and component, its composition, live demo and app usage. A source test checks registered exports, catalog coverage, duplicate ownership and token drift. An accepted baseline tracks remaining exceptions so new work cannot silently increase them.

For Claude or Codex changes, the working sequence is concrete: find the existing Suite pattern, inspect its token and variants, update the shared component when behavior is reusable, then review every consuming app. Keep warehouse dispatch state, staffing approvals and wind diagnostics in their own domain modules. Shared appearance does not justify shared business rules.