Throwaway, development-only prototype. It reads a secret-excluding metadata snapshot from the local catalog PostgreSQL container and never persists changes.

Question being tested: where should the real database-management actions, sensitive-field review, and operation histories live inside the Fleet inventory information architecture?

Run it from frontend/:

npm run prototype:database-management

Then open http://127.0.0.1:5173/?variant=A. The left prototype rail switches among:

A, Fleet Ledger: one dense grid at a time, selection actions inline, detail in a right drawer
B, Fleet Workbench: the same grid beside a persistent contextual rail
C, Fleet Operations Deck: the same grid with actions and history in a bottom console

Every variant uses the same live read-only dataset and the same real action vocabulary. Row actions match production exactly; batch actions appear only after selection. Simulated actions, edits, and sensitive decisions remain in memory and reset on reload. The current local catalog contains one database, 163 tables, 2,275 columns, 5 sensitive flags, 0 relationships, and 21 sync runs. Description and sensitive-suggestion histories are honestly empty because no runs are persisted yet.

The active variant is stored in the URL. Edit files in this directory while Vite is running to see changes immediately through hot reload. Set THT_PROTOTYPE_CATALOG_CONTAINER before starting Vite to read a different local catalog container; if the container is unavailable, a small saved snapshot is displayed and labelled as such. The live snapshot excludes credentials and source rows, but it does include catalog host/base URL metadata, comments, descriptions, and sanitized operation errors.

Generated theme asset

All three Fleet ideas use assets/thoth-cosmic-archive.png, generated with the built-in ImageGen tool in stylized-concept mode. Final prompt: a restrained wide fantasy mural of Thoth as guardian of a celestial archive, with papyrus, stone, and constellation paths suggesting schema relationships; twilight lapis-charcoal and warm porcelain palette; quiet central negative space; no text, logos, watermarks, interface elements, neon, excessive gold, or busy detail behind the data surface.