1.9 KiB
1.9 KiB
Studio Decisions
This directory contains Studio decision records.
Current decision records:
Bank Composition Details DTO Projection Decision.mdBank Composition Base Components Decision.mdBank Composition Section Shell Decision.mdBank Composition Middleware and Staged Editing Decision.mdBank Composition WorkspaceBus Interaction Decision.mdBank Composition Persistence and Snapshot Propagation Decision.md
The first Studio decision wave and the first asset workspace wave were already consolidated into:
Purpose
A Studio decision record bridges UI discussion and implementation.
Use this directory to capture:
- what Studio behavior was chosen,
- why that interaction model was preferred,
- what constraints now apply to the shell and workspaces,
- what specs, plans, and code paths must be updated.
Expected Format
A Studio decision should usually include:
- Title
- Status
- Date or Cycle
- Context
- Decision
- Invariants and Constraints
- Explicit Non-Decisions
- Propagation Targets
- Validation Notes or Examples
Writing Rules
- State the adopted Studio behavior early and clearly.
- Keep the tone stable and implementation-oriented.
- Record interaction constraints explicitly.
- Point to exact specs, plans, or UI surfaces that need propagation.
Implementation Rule
If Studio code work reveals a missing decision, do not guess the UX contract. Return the issue to agenda or decision review.