# Workbenches Handbook

Oshun's workbench estate is a shared governed platform plus seven domain
initiatives: Isis, Metis, Yemaya, Veritas, Euterpe, Aja, and Bellona. This
handbook is the maintained front door to every workbench, their common
interaction and data contracts, and the operational evidence needed to change
them safely.

The **Yemaya Study & Deconstruction Workspace** is also indexed here as **Yemaya
Study Workbench** and **Study Workbench**. “Workspace” is the official product
name; “workbench” is a useful search alias, not a separate product.

## Coverage map

| Aspect                    | Start here                                                                                                | What it covers                                                                                                                                            |
| ------------------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Complete estate           | [Estate and ownership](./estate-and-ownership.md)                                                         | All seven initiatives, shared platform, product purpose, surfaces, services, canonical inventories, and ownership boundaries.                             |
| Yemaya Study Workspace    | [Study Workspace overview](./yemaya-study-workspace.md)                                                   | Users, jobs, journeys, information architecture, media and game study, evidence, comparison, synthesis, learning, accessibility, and honest status.       |
| Study data and operations | [Study data, evidence, learning, and operations](./yemaya-study-data-evidence-learning-and-operations.md) | Identity model, schemas, rights, provenance, search, graph, evaluation, export, deletion, recovery, incidents, and release gates.                         |
| Shared platform           | [Platform and composition](./shared-platform-and-composition.md)                                          | Workbench Kit ownership, shell primitives, tokens, archetypes, extension points, history, jobs, suggestions, provenance, and degradation.                 |
| Trust                     | [Data, rights, security, and safety](./data-rights-security-and-safety.md)                                | Tenancy, authorization, untrusted media, prompt injection, policy, rights expiry, retention, audit, signing, export, and deletion.                        |
| Runtime                   | [Operations, observability, and release](./operations-observability-and-release.md)                       | Dependencies, service health, SLOs, capacity, backups, restore, rollout, rollback, provider failure, and game days.                                       |
| Engineering               | [Development, testing, and change map](./development-testing-and-change-map.md)                           | Code and evidence map, inventory regeneration, contract checks, unit/integration/browser/accessibility/performance/security lanes, and safe change paths. |

## The estate at a glance

| Workbench                           | Primary job                                                                                                               | Characteristic surfaces                                                                                                                             |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Isis governed generation**        | Create and govern image, video, audio, and 3D generation workflows and outputs.                                           | Studio generation pages, workflow/model registries, GPU and service execution, output review, provenance, parity and policy controls.               |
| **Metis courseware and assessment** | Design curricula, learning paths, assessments, classrooms, and outcomes.                                                  | Authoring and learner routes, adaptive learning, assessment/evaluation, analytics, integrations, and service APIs.                                  |
| **Yemaya production and study**     | Run animation/film production surfaces and deconstruct source works into evidence-linked learning and original decisions. | Studio web, desktop, Study Workspace service, media timelines, annotations, notebooks, comparisons, learning paths, exports, and production review. |
| **Veritas newsroom**                | Research, verify, compose, approve, publish, and correct evidence-bearing editorial work.                                 | Newsroom services, publishing and social automation, claims/sources, review, schedules, corrections, and audit.                                     |
| **Euterpe music production**        | Compose, record, edit, mix, collaborate, and perform in a browser/native DAW environment.                                 | DAW, realtime surface, audio engine modules, identity/billing, collaboration, and launch telemetry.                                                 |
| **Aja motion operations**           | Capture, clean, retarget, compare, and deliver motion/reference-video assets.                                             | Studio routes, motion AI/pipeline/reference services, CLI, formats, skeletons, metrics, and operational review.                                     |
| **Bellona DCC and interchange**     | Coordinate builds, renders, approvals, and managed Blender/Godot/Unity/Unreal bridges.                                    | Studio pages, control room, build/render services, DCC bridges, remote hosts, CLI, and mobile approvals.                                            |

The table describes responsibility, not shipment. The machine-readable
[workbench inventory](../../../evidence/v1-workbenches/inventory/README.md) and
domain-specific inventories are the measured snapshot. The
[program ledger](../../../V1_DOMAIN_WORKBENCHES_TODOS_2026-07-23.md) records
requirements and completion evidence. A route, type, or proposal alone does not
prove a supported end-to-end experience.

## Shared workbench model

Every domain keeps its own business language and owns its persistence and
effects. The shared platform supplies reusable mechanics where uniform behavior
is a safety and usability feature:

```mermaid
flowchart LR
  U[User intent] --> S[Domain workbench shell]
  S --> G[Identity, tenant, grants, policy]
  G --> D[Domain commands and queries]
  D --> J[Jobs, history, suggestions, review]
  J --> E[Evidence, provenance, audit]
  E --> O[Domain output or governed side effect]
  O --> R[Observability, recovery, release evidence]
```

The Workbench Kit must not become a domain service. Domain packages may consume
the shared contracts and UI primitives; the shared package may not import a
domain implementation to “help” it. This dependency direction is fixed in
[ADR-S1](../../../docs/adr/ADR-S1-workbench-kit-package-ownership.md).

## Status vocabulary

- **Shipped / wired** means the supported surface reaches its real effect and
  the relevant enforcement and failure paths are tested.
- **Built but unwired** means implementation exists without a supported entry
  path or runtime composition.
- **Gated** means a real path is restricted by tenant policy, permissions,
  credentials, feature scope, review, or rollout state.
- **Proposed** means the design is intentional but must not be presented as a
  current capability.
- **Evidence snapshot** means a generated inventory describes a particular
  audited source revision; regenerate it before relying on counts.

## Reading paths

**Product and design:** begin with [the full estate](./estate-and-ownership.md),
then the domain's source documentation. For study, use the
[Study Workspace overview](./yemaya-study-workspace.md).

**Engineering:** read
[platform and composition](./shared-platform-and-composition.md),
[trust boundaries](./data-rights-security-and-safety.md), and the
[change map](./development-testing-and-change-map.md).

**SRE, security, and governance:** read
[operations](./operations-observability-and-release.md),
[data and rights](./data-rights-security-and-safety.md), and the domain runbooks
linked from those pages.

## Canonical sources

- [V1 workbench program ledger](../../../V1_DOMAIN_WORKBENCHES_TODOS_2026-07-23.md)
  — scope, requirements, evidence, and release definition for shared and domain
  workbenches.
- [Generated estate inventory](../../../evidence/v1-workbenches/inventory/README.md)
  — tracked packages, applications, routes, public symbols, and tests.
- [Workbench Kit README](../../../libs/oshun/workbench-kit/README.md) — public
  API, ownership, runtime classes, targets, and references.
- [UI composition ADR](../../../docs/adr/ADR-S4-ui-composition-and-theming.md) —
  token contract, isolation, archetypes, and accessibility composition.
- [Yemaya Study Workspace proposal](../../../docs/proposals/YEMAYA_STUDY_AND_DECONSTRUCTION_WORKSPACE_PROPOSAL.md)
  — the complete evidence-grounded product and architecture proposal.

## Keeping this handbook true

When a workbench is added, renamed, split, or retired, update the estate table,
its canonical inventory generator, and the Docs Center rail in the same change.
When behavior changes, update the relevant deep dive and link to the governing
contract, test, or runbook rather than copying volatile implementation counts.
Regenerate the Docs Center and run its freshness, integrity, unit, and browser
checks before merging.