---
path: /studio/yemaya/advanced-collaboration-features
surface: studio
domain: yemaya
auth: signed-in + studio entitlement
source: apps/oshun/web/src/app/studio/yemaya/advanced-collaboration-features/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 · Advanced Collaboration Features

## Purpose

Admin lane console for the collaborative edit-lock manager. The Edit-Lock
Concurrency Lane wires `/v1/admin/yemaya/advanced-collaboration-features`:
evaluate a batch of edit-lock requests against the locks held at a given instant
(pessimistic concurrency control) — drop expired locks, grant
compatible/re-entrant locks, and deny conflicts with the conflicting principal.

## Entry points

- No breadcrumb panel on this page.
- Reachable from the Studio index and from the Scheduling quick-action (which
  links here).
- Embedded as the Advanced Collaboration Features Lane inside the Studio Web
  aggregator (`/studio/yemaya/studio-web`).
- Direct URL / bookmark (signed-in + studio entitlement).

## Layout regions

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

- **Workspace panel** (`StudioYemayaAdvancedCollaborationFeaturesWorkspace`,
  `data-yemaya-advanced-collaboration-features-workspace`):
  - `<h1>` "Yemaya Advanced Collaboration Features Workspace"
    (`WorkspaceHeading`).
  - Summary paragraph
    (`data-yemaya-advanced-collaboration-features-summary`).
  - **Edit-Lock Concurrency Lane** — `<h2>` `data-yemaya-acf-lane-heading`, the
    real-backed form lane (loading / unauthorized / error / ready-form /
    result, see States).
- **Route Map panel**
  (`data-yemaya-advanced-collaboration-features-route-map`): `<h2>` "Route Map"
  + five `STUDIO_YEMAYA_ADVANCED_COLLABORATION_FEATURES_ROUTE_MAP` entries.
- **Quick-action panel**: two `quickAction` links.

## States

- [ ] **Loading** — `data-yemaya-acf-loading` "Loading edit-lock manager…" while
      the GET catalog fetch is in flight.
- [ ] **Unauthorized** — `data-yemaya-acf-unauthorized` "Access restricted." on a
      401/403 admin-scope failure (fail-closed).
- [ ] **Error** — `data-yemaya-acf-error` "Could not load the edit-lock manager."
      on a non-OK / malformed catalog response.
- [ ] **Ready-form** — `data-yemaya-acf-form` once the catalog (`summary`,
      `modes`, `compatibility`) resolves; `data-yemaya-acf-engine-summary` shows
      the engine summary.
- [ ] **Result** — `data-yemaya-acf-result` with a `data-yemaya-acf-headline`
      (granted / denied / expired / active counts), a
      `data-yemaya-acf-grants-list`, and a `data-yemaya-acf-denials-list`; or a
      validation message `data-yemaya-acf-eval-error`.

## Interactions

### Edit-Lock form (`data-yemaya-acf-form`)

- [ ] **Held locks + requests (JSON)** — `textarea`
      `data-yemaya-acf-payload` (aria-label "lock payload json"); must parse to a
      JSON object.
- [ ] **Submit** — `button` `data-yemaya-acf-submit` "Evaluate locks" → POST
      `/v1/admin/yemaya/advanced-collaboration-features/evaluate` with the parsed
      `{ now, heldLocks, requests }` payload.

### Route map

`data-yemaya-advanced-collaboration-features-route-map` — five entries:

- [ ] `/studio/yemaya/advanced-collaboration-features`
- [ ] `/studio/yemaya/advanced-collaboration-features/scenes/[sceneId]`
- [ ] `/studio/yemaya/advanced-collaboration-features/exports/[exportId]`
- [ ] `/studio/yemaya/advanced-collaboration-features/revisions/[revisionId]`
- [ ] `/studio/yemaya/advanced-collaboration-features/governance/[policyId]`

### Quick actions

- [ ] **"Open Yemaya Production Management Integrations workspace"** →
      `/studio/yemaya/production-management-integrations`.
- [ ] **"Back to Studio workspace index"** → `/studio`.

## Data & contracts

- **Reads**: GET `/v1/admin/yemaya/advanced-collaboration-features` (catalog:
  `summary`, `modes`, `compatibility`) on mount.
- **Writes**: POST
  `/v1/admin/yemaya/advanced-collaboration-features/evaluate`.
- **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/StudioYemayaAdvancedCollaborationFeaturesWorkspace.tsx`
- Route map source:
  `apps/oshun/web/src/components/studio/StudioYemayaAdvancedCollaborationFeaturesRouteMap.ts`
- Parent aggregator: [`studio-yemaya-studio-web.md`](./studio-yemaya-studio-web.md)
- Sibling Yemaya bridges: see folder index
- Feature spec: [`V1/features.md`](../../../../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 Edit-Lock Concurrency Lane. Confirm whether the copy should be
      trimmed.
- [ ] The Route Map advertises scenes / exports / revisions / governance
      sub-routes that the live lane does not expose.