Studio Hathor · Lore Validation Taxonomy

Purpose#

Admin lane console that validates an era taxonomy — checking the era hierarchy (parent/child relationships, types) for structural validity. The operator supplies a JSON array of eras and the lane returns a valid/clean verdict plus issue counts and a list of taxonomy issues.

Entry points#

• Direct URL / bookmark — yes; alternates.canonical set to /studio/hathor/lore-validation-taxonomy
• Validation hub / Studio overview links — Hathor validation and Studio overview navigation link directly to this lane.
• Studio overview — see ../../studio-overview.md

Layout regions#

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

• Workspace <StudioHathorLoreValidationTaxonomyWorkspace /> (data-hathor-lore-validation-taxonomy-workspace):
  • WorkspaceHeading <h1> — "Hathor Lore Validation Taxonomy Workspace"
  • Summary <p data-hathor-lore-validation-taxonomy-summary>
  • The taxonomy-validation catalog (data-hathor-lvtx-catalog), form lane, pending submit state, validation errors, and result
• Route Map panel data-hathor-lore-validation-taxonomy-route-map — <h2> "Route Map" listing the 5 STUDIO_HATHOR_LORE_VALIDATION_TAXONOMY_ROUTE_MAP entries (events / conflicts / threads / governance child paths)
• Quick-action lane (data-hathor-lvtx-quick-actions, data-hathor-lvtx-quick-action-count="2") — Lore Validation Causality (data-hathor-lvtx-quick-action="lore-validation-causality") and Back to Studio workspace index (data-hathor-lvtx-quick-action="studio-index")

States#

• Loading — data-hathor-lvtx-loading while the GET catalog request is in flight
• Unauthorized (admin-scope 401/403) — data-hathor-lvtx-unauthorized
• Error — data-hathor-lvtx-error
• Ready (form) — data-hathor-lvtx-validate-form with data-hathor-lvtx-form-state="idle", eras textarea, and submit
• Pending submit — data-hathor-lvtx-form-state="validating" and data-hathor-lvtx-submit-state="validating"; submit is disabled with aria-disabled="true" and aria-busy="true" until the BFF response returns
• Result — data-hathor-lvtx-result with data-hathor-lvtx-valid / data-hathor-lvtx-counts and data-hathor-lvtx-issues (per-issue data-hathor-lvtx-issue-item) or data-hathor-lvtx-clean
• Validation error — data-hathor-lvtx-validate-error

Interactions#

Taxonomy validation lane#

• Eras — eras textarea (data-hathor-lvtx-eras, aria-label="eras json"), JSON array of { id, name, type, parentEra? }
• Submit — <button data-hathor-lvtx-validate-submit> "Validate taxonomy" → POST VALIDATE_ENDPOINT

Route Map panel#

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

Quick-action lane#

• "Open Hathor Lore Validation Causality workspace" → /studio/hathor/lore-validation-causality
• "Back to Studio workspace index" → /studio

Data & contracts#

• Reads: GET /v1/admin/hathor/lore-validation-taxonomy (LVTX_ENDPOINT) — the taxonomy validation catalog, rendered as data-hathor-lvtx-catalog
• Writes: POST /v1/admin/hathor/lore-validation-taxonomy/validate (VALIDATE_ENDPOINT) with the eras array. The happy path returns { ok: true, result }; malformed era payloads return BFF 400 reason strings such as invalid_era, which the lane surfaces in data-hathor-lvtx-validate-error.
• 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-lore-validation-causality.md, ./studio-hathor-lore-validation-contradictions.md, ./studio-hathor-lore-validation-timeline.md
• Component sources:
  • apps/oshun/web/src/components/studio/StudioHathorLoreValidationTaxonomyWorkspace.tsx
  • apps/oshun/web/src/components/studio/StudioHathorLoreValidationTaxonomyRouteMap.ts

E2E coverage#

• apps/oshun/web/e2e/studio-hathor-lore-validation-taxonomy.spec.ts — signed-in admin route; real Hathor taxonomy-validation BFF catalog and validate calls; seeded TAXONOMY_CYCLE_DETECTED; edited TAXONOMY_INVALID_TYPE; clean age → epoch nesting; warning TAXONOMY_HIERARCHY_VIOLATION; malformed JSON and empty-array zero-POST branches; live BFF invalid_era 400 detail; catalog loading/error; pending submit lockout; non-admin fail-closed state; anonymous redirect; route-map and quick-action anchors; automated 44px checks for the main editable controls and quick actions; shared axe gate.
• Supporting route contract coverage: apps/oshun/bff/src/__tests__/admin-hathor-lore-validation-taxonomy-route.test.ts covers auth/scope, issue-code/type catalog, invalid type, missing parent, cycle detection, valid nesting, disallowed nesting warnings, and BFF 400 payload validation.

Open questions / known gaps#

• Hathor is confirmed in V1 per WALKTHROUGH/matrix/routes.csv and WALKTHROUGH/matrix/coverage.md (product-owner confirmation recorded 2026-05-29 for Bellona / Hathor / Neith).
• Manual screen-reader pass remains for the live browser surface; automated axe and touch-target coverage now pass for the route-level controls.