65 lines
2.6 KiB
Markdown
65 lines
2.6 KiB
Markdown
# Studio Agendas
|
|
|
|
This directory contains active Studio discussion agendas.
|
|
|
|
## Active Agendas
|
|
|
|
The initial Studio UI planning wave is:
|
|
|
|
1. [`01.1. Asset Workspace Information Architecture Agenda.md`](./01.1.%20Asset%20Workspace%20Information%20Architecture%20Agenda.md)
|
|
2. [`01.2. Asset List, Filters, and Selection Model Agenda.md`](./01.2.%20Asset%20List,%20Filters,%20and%20Selection%20Model%20Agenda.md)
|
|
3. [`01.3. Asset Details, Diagnostics, and Action Surface Agenda.md`](./01.3.%20Asset%20Details,%20Diagnostics,%20and%20Action%20Surface%20Agenda.md)
|
|
4. [`01.4. Background Events, Progress, and Activity Feed Agenda.md`](./01.4.%20Background%20Events,%20Progress,%20and%20Activity%20Feed%20Agenda.md)
|
|
5. [`01.5. Preview, Confirm, and Apply Mutation Flows Agenda.md`](./01.5.%20Preview,%20Confirm,%20and%20Apply%20Mutation%20Flows%20Agenda.md)
|
|
6. [`01.6. Studio UI Foundations - Naming, Events, and Custom Components Agenda.md`](./01.6.%20Studio%20UI%20Foundations%20-%20Naming,%20Events,%20and%20Custom%20Components%20Agenda.md)
|
|
7. [`01.7. Studio Components Module and Admission Policy Agenda.md`](./01.7.%20Studio%20Components%20Module%20and%20Admission%20Policy%20Agenda.md)
|
|
|
|
Recommended discussion order:
|
|
|
|
`01.6 -> 01.7 -> 01.1 -> 01.2 -> 01.3 -> 01.4 -> 01.5`
|
|
|
|
The Studio shell baseline was closed in [`../decisions/001-studio-shell-workspace-navigation-and-layout-decision.md`](../decisions/001-studio-shell-workspace-navigation-and-layout-decision.md).
|
|
|
|
The remaining order closes the shared UI foundations, then the components admission policy, then the asset workspace structure, and only after that the detailed interaction flows.
|
|
|
|
## 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.
|