Studio Hathor · Database

Purpose#

Aggregator surface for the Hathor data-persistence cluster. It mounts a Capability Summary plus two embedded lanes — the Simulation State Persistence lane and the World Configuration lane — so save/restore durability and world record governance are reachable from one page. It issues no /v1 fetch of its own; each embedded lane owns its data.

Entry points#

• Direct URL / bookmark — /studio/hathor/database; alternates.canonical is set.
• Breadcrumb / quick-action — Studio › Hathor Simulation State Persistence › Database; this page links to Simulation State Persistence, World Configuration, and World Version Branching.
• Studio overview — see ../../studio-overview.md.

Layout regions#

page.tsx renders inside <ShellLayout active="studio">:

• Breadcrumb panel (<section data-hathor-database-breadcrumbs>): Studio → Hathor Simulation State Persistence → Database (current).
• Workspace (StudioHathorDatabaseWorkspace, data-hathor-database-workspace):
  • <h1> WorkspaceHeading — "Hathor Database Workspace"
  • Summary <p data-hathor-database-summary>
  • Capability Summary (data-hathor-database-capability-summary, <h2>): 4 capability cards.
  • Simulation State Persistence Lane (data-hathor-database-state-persistence-lane, <h2>): embeds StudioHathorSimulationStatePersistenceWorkspace.
  • World Configuration Lane (data-hathor-database-world-configuration-lane, <h2>): embeds StudioHathorWorldConfigurationWorkspace.
• Route Map panel (<section data-hathor-database-route-map>, <h2>Route Map</h2>): 6 entries from STUDIO_HATHOR_DATABASE_ROUTE_MAP.
• Quick-action lane (className="quickAction" Links): Simulation State Persistence, World Configuration, World Version Branching, Back to Studio workspace index.

States#

• Simulation State Persistence lane — Loading / Unauthorized / Error / Ready-form / Result, per its own doc (./studio-hathor-simulation-state-persistence.md).
• World Configuration lane — the dense-operator workspace with its own list/detail/wizard, BFF records hydration, and parity/observability panels, per its own doc (./studio-hathor-world-configuration.md).

Interactions#

• Embedded lane interactions — delegated to the two child workspaces; see their docs for fields and submit verbs.
• Route Map entries — verify against STUDIO_HATHOR_DATABASE_ROUTE_MAP (6 entries).
• Quick-action links — Simulation State Persistence (/studio/hathor/simulation-state-persistence), World Configuration (/studio/hathor/world-configuration), World Version Branching (/studio/hathor/world-version-branching), Back to Studio (/studio).

Data & contracts#

• Reads / Writes: none from this aggregator; the embedded lanes own their contracts (/v1/admin/hathor/simulation-state-persistence and /v1/studio/hathor/world-configuration/records).
• Realtime: none.
• Caching: n/a here; each child lane fetches on mount, cache: 'no-store'.
• Auth: route is behind the signed-in + studio proxy gate; the embedded persistence lane is admin-scoped and fail-closed.

Cross-references#

• Parent: ../../studio-overview.md
• Component sources:
  • apps/oshun/web/src/components/studio/StudioHathorDatabaseWorkspace.tsx
  • apps/oshun/web/src/components/studio/StudioHathorDatabaseRouteMap.ts
  • Embeds StudioHathorSimulationStatePersistenceWorkspace, StudioHathorWorldConfigurationWorkspace
• Siblings: ./studio-hathor-simulation-state-persistence.md, ./studio-hathor-world-configuration.md, ./studio-hathor-world-version-branching.md

Open questions / known gaps#

• Hathor is unconfirmed-v1 per WALKTHROUGH/matrix/routes.csv; confirm whether the dedicated /studio/hathor/* surfaces ship V1 or are internal-only.
• The embedded World Configuration lane is the older dense-operator template (fixtures + wizard + telemetry) rather than a lane console; confirm whether it should be reduced to a single real-backed lane like its siblings.