Studio Hathor · Location Modeling

Purpose#

Admin lane console that assesses a single location record — condition, danger level, atmosphere, services, demographics, economy, trade routes, districts, and defenses — and returns scored diagnostics. The operator submits a JSON location object and the lane returns the assessment scores.

Entry points#

• Quick-action link from /studio/hathor/character-modeling and /studio/hathor/domain-models (verify against those pages' sources)
• Direct URL / bookmark — yes; alternates.canonical set to /studio/hathor/location-modeling
• Studio overview — see ../../studio-overview.md

Layout regions#

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

• Workspace <StudioHathorLocationModelingWorkspace /> (data-hathor-location-modeling-workspace):
  • WorkspaceHeading <h1> — "Hathor Location Modeling Workspace"
  • Summary <p data-hathor-location-modeling-summary>
  • Location Assessment Lane — <h2 data-loc-lane-heading>; holds the loading / unauthorized / error / form / result states
• Route Map panel data-hathor-location-modeling-route-map — <h2> "Route Map" listing the 5 STUDIO_HATHOR_LOCATION_MODELING_ROUTE_MAP entries (locations / landmarks / travel-routes / governance child paths)
• Quick-action lane — three Link.quickAction anchors: Character Modeling, Timeline Modeling, Back to Studio workspace index

States#

• Loading — data-loc-loading while the GET catalog request is in flight
• Unauthorized (admin-scope 401/403) — data-loc-unauthorized
• Error — data-loc-error
• Ready (form) — data-loc-enums enum hint + location textarea + submit
• Result — data-loc-result with data-loc-headline and data-loc-scores
• Validation error — data-loc-assess-error

Interactions#

Location Assessment Lane#

• Location payload — <textarea data-loc-payload>, JSON { location:{ locationId, name, condition, dangerLevel, atmosphere, services[], hasDemographics, economyActivity, tradeRoutes, districts[], defenses? } }
• Submit — <button data-loc-submit> "Assess location" → POST ASSESS_ENDPOINT

Route Map panel#

• Route entries — verify match with STUDIO_HATHOR_LOCATION_MODELING_ROUTE_MAP (5 entries)

Quick-action lane#

• "Open Hathor Character Modeling workspace" → /studio/hathor/character-modeling
• "Open Hathor Timeline Modeling workspace" → /studio/hathor/timeline-modeling
• "Back to Studio workspace index" → /studio

Data & contracts#

• Reads: GET /v1/admin/hathor/workbench-locations (LOC_ENDPOINT; note the endpoint slug differs from the route slug — it reuses the workbench-locations admin backend) — the location enums catalog
• Writes: POST /v1/admin/hathor/workbench-locations/assess (ASSESS_ENDPOINT) with the location record
• Realtime: none
• Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders()
• Auth/role check: admin-scoped, fail-closed on 401/403; route additionally gated signed-in + studio by the BFF proxy

Cross-references#

• Parent: ../../studio-overview.md
• Shell: ../../../shell/04-auth-session.md
• Sibling routes: ./studio-hathor-character-modeling.md, ./studio-hathor-timeline-modeling.md, ./studio-hathor-domain-models.md
• Component sources:
  • apps/oshun/web/src/components/studio/StudioHathorLocationModelingWorkspace.tsx
  • apps/oshun/web/src/components/studio/StudioHathorLocationModelingRouteMap.ts

Open questions / known gaps#

• The GET/POST endpoints live under workbench-locations, not location-modeling. Confirm the shared backend is intentional.
• Hathor is unconfirmed-v1 per WALKTHROUGH/matrix/routes.csv. Confirm whether the dedicated /studio/hathor/ lane consoles ship at V1 or are internal-only.