58 lines
2.3 KiB
Markdown
58 lines
2.3 KiB
Markdown
# Studio Agendas
|
|
|
|
This directory contains active Studio discussion agendas.
|
|
|
|
Active agendas:
|
|
|
|
- [`Palette Management in Studio Agenda.md`](./Palette%20Management%20in%20Studio%20Agenda.md)
|
|
- [`Asset Bank Composition Area - Dual List and Capacity Meter Agenda.md`](./Asset%20Bank%20Composition%20Area%20-%20Dual%20List%20and%20Capacity%20Meter%20Agenda.md)
|
|
- [`Agenda-01-Asset-Bank-Composition-Snapshot-Transfer-to-Details-DTOs.md`](./Agenda-01-Asset-Bank-Composition-Snapshot-Transfer-to-Details-DTOs.md)
|
|
- [`Agenda-02-Asset-Bank-Composition-Base-Components.md`](./Agenda-02-Asset-Bank-Composition-Base-Components.md)
|
|
- [`Agenda-03-Asset-Bank-Composition-Section-Shell.md`](./Agenda-03-Asset-Bank-Composition-Section-Shell.md)
|
|
- [`Agenda-04-Asset-Bank-Composition-Middleware-and-Staged-Editing.md`](./Agenda-04-Asset-Bank-Composition-Middleware-and-Staged-Editing.md)
|
|
- [`Agenda-05-Asset-Bank-Composition-WorkspaceBus-Interaction.md`](./Agenda-05-Asset-Bank-Composition-WorkspaceBus-Interaction.md)
|
|
- [`Agenda-06-Asset-Bank-Composition-Persistence-and-Snapshot-Propagation.md`](./Agenda-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/`](../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.
|