prometeu-studio/docs/studio/agendas

Studio Agendas

This directory contains active Studio discussion agendas.

Active Agendas

The initial Studio UI planning wave is:

1. 01.2. Asset List, Filters, and Selection Model Agenda.md
2. 01.3. Asset Details, Diagnostics, and Action Surface Agenda.md
3. 01.4. Background Events, Progress, and Activity Feed Agenda.md
4. 01.5. Preview, Confirm, and Apply Mutation Flows Agenda.md

Recommended discussion order:

01.2 -> 01.3 -> 01.4 -> 01.5

The shell, UI foundations, and components admission baselines were already consolidated into ../specs/ and ../learn/.

The asset workspace information architecture baseline is already closed in ../decisions/004-asset-workspace-information-architecture-decision.md.

The remaining order closes the detailed interaction model on top of that structure.

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.