Studio · Yemaya · Asset Organization

Purpose#

Admin lane console wired to the @yemaya/asset-library living-scene lineage DAG: supply a set of artifacts plus derivation edges and resolve a target artifact's lineage — its ancestors (what produced it) and descendants (what derives from it) — with unknown-node, duplicate, and cycle validation.

Entry points#

• Studio index quick-actions.
• No breadcrumb panel on this page.
• This page links out to /studio/yemaya/asset-pipeline.
• Direct URL / bookmark (signed-in + studio entitlement).

Layout regions#

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

• Workspace panel (StudioYemayaAssetOrganizationWorkspace, data-yemaya-asset-organization-workspace):
  • <h1> "Yemaya Asset Organization Workspace".
  • Summary <p data-yemaya-asset-organization-summary> (lineage / ancestors / descendants with cycle and unknown-node validation).
  • Lineage lane — loading / unauthorized / error / ready-form / result.
• Route Map panel (data-yemaya-asset-organization-route-map): <h2> "Route Map" with five entries.
• Quick-action panel: two quickAction links.

States#

• Loading — data-yemaya-ao-loading ("Loading lineage engine…").
• Unauthorized — 401/403 → data-yemaya-ao-unauthorized with reason "Yemaya workspace scope required to view asset organization.".
• Error — non-OK / malformed catalog → data-yemaya-ao-error.
• Ready-form — catalog (edgeKinds) loaded: the lineage form renders.
• Result — 200 → data-yemaya-ao-result with data-yemaya-ao-ancestors, data-yemaya-ao-descendants, data-yemaya-ao-counts.
• Validation error — invalid JSON, empty/non-array nodes, empty target artifact, or a non-200 POST → data-yemaya-ao-lineage-error.

Interactions#

Lineage lane#

<form data-yemaya-ao-lineage-form>:

• Artifact nodes (JSON) — <textarea data-yemaya-ao-field-nodes> (aria-label "artifact nodes json"), seeded [{ artifactId }].
• Lineage edges (JSON) — <textarea data-yemaya-ao-field-edges> (aria-label "lineage edges json"), [{ parentArtifactId, childArtifactId, kind? }].
• Target artifact — <input data-yemaya-ao-field-artifact> (aria-label "target artifact").
• "Resolve lineage" submit (data-yemaya-ao-lineage-submit) — POSTs { nodes, edges, artifactId }.

Route map#

data-yemaya-asset-organization-route-map — five entries:

• /studio/yemaya/asset-organization
• /studio/yemaya/asset-organization/collections/[collectionId]
• /studio/yemaya/asset-organization/classification/[classificationId]
• /studio/yemaya/asset-organization/lineage/[lineageId]
• /studio/yemaya/asset-organization/governance/[policyId]

Quick actions#

• "Open Yemaya Asset Pipeline workspace" → /studio/yemaya/asset-pipeline.
• "Back to Studio workspace index" → /studio.

Data & contracts#

• Reads: GET /v1/admin/yemaya/asset-organization (catalog; edgeKinds) on mount with buildBffAuthHeaders(), cache: 'no-store'.
• Writes: POST /v1/admin/yemaya/asset-organization/lineage → { lineage: { artifactId, ancestors[], descendants[], nodeCount, edgeCount } }.
• Realtime: None.
• Caching: client fetch on mount, no-store; aborted on unmount.
• Auth/role check: admin-scoped, fail-closed; route additionally signed-in + studio via the proxy gate.

Cross-references#

• Workspace source: apps/oshun/web/src/components/studio/StudioYemayaAssetOrganizationWorkspace.tsx
• Route map source: apps/oshun/web/src/components/studio/StudioYemayaAssetOrganizationRouteMap.ts
• Page source: apps/oshun/web/src/app/studio/yemaya/asset-organization/page.tsx
• Sibling: studio-yemaya-assets.md
• Studio overview: studio-overview.md
• Feature spec: V1/features.md

Open questions / known gaps#

• Nodes/edges are entered as raw JSON; verify whether a visual graph editor is planned.
• Route-map children (collections/classification/lineage/governance) are a sitemap contract; confirm which dynamic pages exist.