# Studio Learn

This directory contains didactic Studio knowledge.

## Purpose

`learn/` exists to teach the Studio model, not merely to store old discussion output.

Use it to:

- explain why the Studio shell is structured the way it is,
- connect UI decisions to practical implementation,
- document common integration pitfalls,
- help future contributors navigate the workspaces and background event model.

## What Belongs Here

A Studio `learn` artifact should usually include:

1. the original UX or architecture problem,
2. the decision that resolved it,
3. the implemented or specified final model,
4. practical examples or flows,
5. common mistakes and warnings,
6. links to relevant specs and plans.

## Writing Rules

- Prefer didactic structure over historical accumulation.
- Explain why the Studio model exists, not only what it is.
- Keep terminology aligned with Studio specs.
- Refactor older material when the directory stops feeling like a clear learning path.

## Refactor Rule

This directory should be periodically reorganized for better presentation.

If content grows, prefer:

- thematic grouping,
- overview documents,
- explicit learning paths,
- consolidation of duplicated explanations.

## Current Learning Path

Start here:

1. [`mental-model-studio-shell.md`](./mental-model-studio-shell.md)
2. [`mental-model-studio-events-and-components.md`](./mental-model-studio-events-and-components.md)
3. [`mental-model-assets-workspace.md`](./mental-model-assets-workspace.md)
4. [`mental-model-asset-mutations.md`](./mental-model-asset-mutations.md)