# Studio Agendas

This directory contains active Studio discussion agendas.

There are currently no active Studio agendas.

The shell, UI foundations, components admission baselines, and the first asset workspace wave were already consolidated into [`../specs/`](../specs/) and [`../learn/`](../learn/).

## Purpose

An agenda exists to drive a decision.

Use an agenda when:

- the Studio UI topic is still open,
- multiple interaction models are possible,
- the team still needs tradeoffs and a recommendation,
- implementation would otherwise guess shell or UX behavior.

## Expected Format

A Studio agenda should usually include:

1. Title
2. Status
3. Purpose
4. Domain Owner
5. Current Code Context
6. Options
7. Tradeoffs
8. Recommendation
9. Open Questions
10. Expected Follow-up

## Writing Rules

- Keep the document centered on unresolved Studio behavior.
- Anchor the discussion in the actual `prometeu-studio` shell and workspaces.
- Distinguish clearly between shell decisions, workspace decisions, and service-integration decisions.
- Prefer concrete interaction tradeoffs over generic design commentary.

## Exit Rule

An agenda should leave the active set when:

- the main UX tradeoffs are understood,
- a recommendation is ready to adopt,
- and the topic is ready to become a decision record.
