---
path: /studio/yemaya/scheduling
surface: studio
domain: yemaya
auth: signed-in + studio entitlement
source: apps/oshun/web/src/app/studio/yemaya/scheduling/page.tsx
status: walked
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)'
---

# Studio · Yemaya · Scheduling

## Purpose

Admin lane console for production scheduling. It wires the real
`@yemaya/budget-management` TimelineManager via `/v1/admin/yemaya/scheduling`:
supply production tasks with dependencies and get the dependency-first
(topologically ordered) schedule plus the critical path.

## Entry points

- No breadcrumb panel on this page.
- Reachable from the Studio index and from sibling Yemaya routes.
- Direct URL / bookmark (signed-in + studio entitlement).

## Layout regions

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

- **Workspace panel** (`StudioYemayaSchedulingWorkspace`,
  `data-yemaya-scheduling-workspace`):
  - `<h1>` "Yemaya Scheduling Workspace" (`WorkspaceHeading`).
  - Summary paragraph (`data-yemaya-scheduling-summary`).
  - The schedule-generation form lane (loading / unauthorized / error /
    ready-form / result, see States).
- **Route Map panel** (`data-yemaya-scheduling-route-map`): `<h2>` "Route Map" +
  five `STUDIO_YEMAYA_SCHEDULING_ROUTE_MAP` entries.
- **Quick-action panel**: two `quickAction` links.

## States

- [ ] **Loading** — `data-yemaya-sch-loading` "Loading scheduler…" while the GET
      catalog fetch is in flight.
- [ ] **Unauthorized** — `data-yemaya-sch-unauthorized` "Access restricted." on a
      401/403 admin-scope failure (fail-closed).
- [ ] **Error** — `data-yemaya-sch-error` "Could not load scheduling." on a
      non-OK / malformed catalog response.
- [ ] **Ready-form** — `data-yemaya-sch-schedule-form` once the catalog
      (`outputs`) resolves.
- [ ] **Result** — `data-yemaya-sch-result` with `data-yemaya-sch-order`,
      `data-yemaya-sch-critical`, and `data-yemaya-sch-count`; or a validation
      message `data-yemaya-sch-schedule-error`.

## Interactions

### Schedule form (`data-yemaya-sch-schedule-form`)

- [ ] **Tasks (JSON)** — `textarea` `data-yemaya-sch-field-tasks` (aria-label
      "tasks json"); a non-empty JSON array of
      `{ id, duration, dependencies[], critical? }`.
- [ ] **Submit** — `button` `data-yemaya-sch-schedule-submit` "Generate schedule"
      → POST `/v1/admin/yemaya/scheduling/schedule` with `{ tasks }`.

### Route map

`data-yemaya-scheduling-route-map` — five entries:

- [ ] `/studio/yemaya/scheduling`
- [ ] `/studio/yemaya/scheduling/scenes/[sceneId]`
- [ ] `/studio/yemaya/scheduling/exports/[exportId]`
- [ ] `/studio/yemaya/scheduling/revisions/[revisionId]`
- [ ] `/studio/yemaya/scheduling/governance/[policyId]`

### Quick actions

- [ ] **"Open Yemaya Advanced Collaboration Features workspace"** →
      `/studio/yemaya/advanced-collaboration-features`.
- [ ] **"Back to Studio workspace index"** → `/studio`.

## Data & contracts

- **Reads**: GET `/v1/admin/yemaya/scheduling` (catalog: `outputs`) on mount.
- **Writes**: POST `/v1/admin/yemaya/scheduling/schedule`.
- **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`](../../studio-overview.md)
- Workspace source:
  `apps/oshun/web/src/components/studio/StudioYemayaSchedulingWorkspace.tsx`
- Route map source:
  `apps/oshun/web/src/components/studio/StudioYemayaSchedulingRouteMap.ts`
- Engine: `@yemaya/budget-management` (TimelineManager)
- Sibling per-view doc:
  [`studio-yemaya-advanced-collaboration-features.md`](./studio-yemaya-advanced-collaboration-features.md)
- Feature spec: [`V1/features.md`](../../../../V1/features.md)

## Open questions / known gaps

- [ ] The Route Map advertises scenes / exports / revisions / governance
      sub-routes that the live schedule lane does not expose.