HUD guide and screen directory

The spatial HUD is a React/TypeScript application built with Vite, separate from this Next.js documentation website.

Information workspaces

The catalog covers subsystem evidence, agent workspaces, dialogue, cameras, activity and diagnostics. The screen directory documents every declared route. A screen contract does not imply a dedicated adapter or a live source.

Motion, GSAP, Three.js and CSS support transitions, decoded text and the orb. Public-display protection hides private projections. Transparent styling still needs optical testing on the real panel, ambient light and backgrounds.

Read paths and owner consent

Read APIs expose connection metadata, catalog, snapshots, sources, activity and live events. Source observation times, stale flags and HUD fetch times have different meanings, and the panel shows them apart.

The #/agents/edith/approvals workspace can accept or reject pending deferred actions. This is the explicit consent exception to the information display; other observation screens do not become general tool consoles.

Develop and verify

From clients/hud-spatial run npm ci, npm run dev, npm test, npm run build and npm run test:browser as appropriate. Configure the private gateway server-side. Never put root credentials in browser-prefixed configuration.

The build and the predev scripts regenerate the HUD catalog first, so a screen contract that has drifted from the registry fails the build rather than shipping.

Implementation sources

Repository paths below describe the implementation. They do not certify a running deployment or a configured external account.

  • clients/hud-spatial/package.json
  • clients/hud-spatial/src/App.tsx
  • src/mushegh/brain/hud_sources.py
  • src/mushegh/brain/hud_gateway.py

Subsystem directory · HUD guide · Verification and known limits

All 169 declared screen contracts

Fleet

Operations

Voice gateway

Subsystems

Specialists

Council seats