Studio Agendas
This directory contains active Studio discussion agendas.
Active agendas:
Asset Bank Composition Area - Dual List and Capacity Meter Agenda.mdAgenda-01-Asset-Bank-Composition-Snapshot-Transfer-to-Details-DTOs.mdAgenda-02-Asset-Bank-Composition-Base-Components.mdAgenda-03-Asset-Bank-Composition-Section-Shell.mdAgenda-04-Asset-Bank-Composition-Middleware-and-Staged-Editing.mdAgenda-05-Asset-Bank-Composition-WorkspaceBus-Interaction.mdAgenda-06-Asset-Bank-Composition-Persistence-and-Snapshot-Propagation.md
The shell, UI foundations, components admission baselines, and the first asset workspace wave were already consolidated into ../specs/ and ../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:
- Title
- Status
- Purpose
- Domain Owner
- Current Code Context
- Options
- Tradeoffs
- Recommendation
- Open Questions
- Expected Follow-up
Writing Rules
- Keep the document centered on unresolved Studio behavior.
- Anchor the discussion in the actual
prometeu-studioshell 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.