Studio · Yemaya · Gameplay Design

Purpose#

Admin lane console for inspecting the Project Obsidian gameplay design document. The Game Design Operations Lane wires the real @yemaya/project-obsidian ObsidianGameDesign reference via /v1/admin/yemaya/gameplay-design: read its six-phase core loop and seven gameplay systems (investigation, interrogation, deduction, stealth, tactical combat, character progression, UI/UX) and resolve each system's config.

Entry points#

• No breadcrumb panel on this page.
• Reachable from the Studio index and from the NPC Systems quick-action (which links here).
• Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

page.tsx renders ShellLayout active="studio" and:

• Workspace panel (StudioYemayaGameplayDesignWorkspace, data-yemaya-gameplay-design-workspace):
  • <h1> "Yemaya Gameplay Design Workspace" (WorkspaceHeading).
  • Summary paragraph (data-yemaya-gameplay-design-summary).
  • Game Design Operations Lane — <h2> data-yemaya-gd-lane-heading, the real-backed form lane (loading / unauthorized / error / ready-form / result, see States).
• Route Map panel (data-yemaya-gameplay-design-route-map): <h2> "Route Map" + five STUDIO_YEMAYA_GAMEPLAY_DESIGN_ROUTE_MAP entries.
• Quick-action panel: two quickAction links.

States#

• Loading — data-yemaya-gd-loading "Loading game design engine…" while the GET catalog fetch is in flight.
• Unauthorized — data-yemaya-gd-unauthorized "Access restricted." on a 401/403 admin-scope failure (fail-closed).
• Error — data-yemaya-gd-error "Could not load the game design engine." on a non-OK / malformed catalog response.
• Ready-form — data-yemaya-gd-form once the catalog resolves; data-yemaya-gd-engine-summary + a data-yemaya-gd-constants list.
• Result — data-yemaya-gd-result with data-yemaya-gd-headline (the system name) and a data-yemaya-gd-config JSON block; or a validation message data-yemaya-gd-resolve-error.

Interactions#

Operations form (data-yemaya-gd-form)#

• Design system — select data-yemaya-gd-system populated from catalog.systems.
• Submit — button data-yemaya-gd-submit "Inspect system" → POST /v1/admin/yemaya/gameplay-design/system with { system }.

Route map#

data-yemaya-gameplay-design-route-map — five entries:

• /studio/yemaya/gameplay-design
• /studio/yemaya/gameplay-design/scenes/[sceneId]
• /studio/yemaya/gameplay-design/exports/[exportId]
• /studio/yemaya/gameplay-design/revisions/[revisionId]
• /studio/yemaya/gameplay-design/governance/[policyId]

Quick actions#

• "Open Yemaya Location Management workspace" → /studio/yemaya/location-management.
• "Back to Studio workspace index" → /studio.

Data & contracts#

• Reads: GET /v1/admin/yemaya/gameplay-design (catalog: summary, systems, constants) on mount.
• Writes: POST /v1/admin/yemaya/gameplay-design/system.
• Realtime: none.
• Caching: client fetch on mount, cache: 'no-store', buildBffAuthHeaders().
• Auth/role check: admin-scoped fail-closed (401/403 → unauthorized state) behind the proxy studio gate.

Cross-references#

• Studio overview: studio-overview.md
• Workspace source: apps/oshun/web/src/components/studio/StudioYemayaGameplayDesignWorkspace.tsx
• Route map source: apps/oshun/web/src/components/studio/StudioYemayaGameplayDesignRouteMap.ts
• Engine: @yemaya/project-obsidian (ObsidianGameDesign)
• Sibling per-view doc: studio-yemaya-npc-systems.md
• Feature spec: V1/features.md

Open questions / known gaps#

• The summary paragraph still advertises "dense expert-mode controls, progressive disclosure" — leftover legacy copy; the live surface is the single Game Design Operations Lane.
• The Route Map advertises scenes / exports / revisions / governance sub-routes that the live lane does not expose.