V1 Web PWA · Surface walkthrough

Studio Hathor · Lore Compiler

A per-surface walkthrough of the V1 Web PWA studio surface: layout, states, interactions, data, and cross-references.

walked
8sections2 minread
Markdown source
On this page

Context. surface studio · domain hathor · route /studio/hathor/lore-compiler · auth signed-in + studio entitlement · source apps/oshun/web/src/app/studio/hathor/lore-compiler/page.tsx

Last walked. 2026-05-29 automated runtime walk (Playwright headless) — render, /v1 data (2xx), console/page-errors, expected content, screenshot verified; live screen-reader, touch, offline, and telemetry-delivery checks pending a manual AT pass. Evidence: WALKTHROUGH/results/runtime-sweep-2026-05-29.md; body re-derived 2026-06-03 from current source (lane-console architecture)

Purpose#

Aggregator surface that composes Hathor's lore-compilation lanes: a Capability Summary plus the embedded Chronicle Parser, Lore Compilation for Engines, and Screenplay Compilation workspaces. The page itself issues no /v1 fetch — each embedded lane owns its own admin-scoped, fail-closed backend wiring.

Entry points#

  • Breadcrumb — Studio › Hathor Chronicle Parser › Lore Compiler
  • Quick-action links to chronicle-parser, lore-compilation-for-engines, screenplay-compilation, and Back to Studio
  • Direct URL / bookmark — yes; alternates.canonical set
  • Studio overview — see ../../studio-overview.md

Layout regions#

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

  • Breadcrumb panel (data-hathor-lore-compiler-breadcrumbs): Studio → Hathor Chronicle Parser → Lore Compiler (current)
  • Workspace <section data-hathor-lore-compiler-workspace>:
    • <h1> (WorkspaceHeading) "Hathor Lore Compiler Workspace"
    • Summary <p data-hathor-lore-compiler-summary>
    • Capability Summary (data-hathor-lore-compiler-capability-summary, <h2>)
    • Chronicle Parser Lane (data-hathor-lore-compiler-chronicle-parser-lane, <h2>) → <StudioHathorChronicleParserWorkspace />
    • Lore Compilation for Engines Lane (data-hathor-lore-compiler-lore-compilation-lane, <h2>) → <StudioHathorLoreCompilationForEnginesWorkspace />
    • Screenplay Compilation Lane (data-hathor-lore-compiler-screenplay-lane, <h2>) → <StudioHathorScreenplayCompilationWorkspace />
  • Route Map panel (data-hathor-lore-compiler-route-map): <h2> "Route Map"
    • 6 entries from STUDIO_HATHOR_LORE_COMPILER_ROUTE_MAP
  • Quick-action lane: four Link.quickAction anchors (see Entry points)

States#

This page owns no fetch; each embedded lane carries its own loading / unauthorized / error / ready / result states:

Interactions#

Embedded lanes#

  • Chronicle Parser Lane
  • Lore Compilation for Engines Lane
  • Screenplay Compilation Lane

Route Map panel#

  • 6 route entries — verify match with STUDIO_HATHOR_LORE_COMPILER_ROUTE_MAP

Quick-action lane#

  • "Open Hathor Chronicle Parser workspace" (→ /studio/hathor/chronicle-parser)
  • "Open Hathor Lore Compilation for Engines workspace" (→ /studio/hathor/lore-compilation-for-engines)
  • "Open Hathor Screenplay Compilation workspace" (→ /studio/hathor/screenplay-compilation)
  • "Back to Studio workspace index" (→ /studio)

Data & contracts#

  • Reads / Writes: none at the aggregator level; embedded lanes own their /v1/admin/hathor/* fetches (Chronicle Parser → /chronicle-parser, Screenplay → /screenplay-compilation)
  • Realtime: none
  • Caching: embedded client fetches use cache: 'no-store' + buildBffAuthHeaders
  • Auth/role check: each embedded lane is admin-scoped fail-closed; route is behind the signed-in + studio proxy gate

Cross-references#

Open questions / known gaps#

  • Hathor is unconfirmed-v1 per WALKTHROUGH/matrix/routes.csv. Confirm whether the dedicated /studio/hathor/* admin lane consoles ship in V1.
  • Route Map advertises chronicle-parser/, lore-bundles/, screenplay/, parity/, and governance/ sub-routes with no page.tsx yet.