4.1 KiB
Studio Specs
This directory contains the normative Studio specification set.
Purpose
Specs define the official Studio contract.
They exist to stabilize:
- the application shell,
- workspace responsibilities,
- interaction flows,
- service and event integration expectations,
- UX behavior that implementation should preserve.
Expected Format
The exact structure may vary by document, but a Studio spec should usually contain:
- Title
- Status
- Scope or Applies To
- Purpose
- Authority and Precedence
- Normative Inputs
- Core Rules
- Non-Goals
- Exit Criteria
Writing Rules
- Write in normative language.
- Integrate only decisions that have already been closed.
- Keep design exploration and option analysis out of the spec body.
- Preserve clear boundaries between shell, workspace, and integration specs.
Upstream Rule
Specs should normally be fed by:
- agendas that frame the open Studio topic,
- decisions that close the product or interaction choice,
- plans that define propagation,
- then spec integration.
If a spec edit would require guessing unresolved UI behavior, stop and surface the missing decision first.
Current Corpus
The current Studio core corpus is:
1. Studio Shell and Workspace Layout Specification.md2. Studio UI Foundations Specification.md3. Studio Components Module Specification.md4. Assets Workspace Specification.md8. Project-Local Studio State Specification.md9. Studio Core and Adapter Architecture Specification.md10. DEV and Automation Specification.md11. MCP Tools and Project Knowledge Contract.md
Reading Order
Recommended order:
- shell and workspace layout;
- shared UI foundations;
- components module policy;
- assets workspace behavior;
- project-local Studio state behavior;
- Studio Core, adapter, composition, and external integration boundaries;
- DEV authority, document handoff, automation operations/captures and phased integration gates;
- MCP transport/tool schemas and project/language knowledge contracts.
Current Wave Notes
The embedded Studio code-editor stack was removed by DEC-0031.
Normative reminders:
- the accepted Studio workspace corpus is
Assets,Debug,Shipper, andDEV; the DEV implementation follows DEC-0060's phased delivery; - project-local Studio session state remains normative and is owned by
StudioProjectSession; - DEC-0060 authorizes an external coding agent using native file tools and the existing project LSP through MCP; it does not reinstate the embedded editor or authorize a replacement language-service architecture;
- the Studio backend is exposed through neutral API contracts shared by JavaFX and the local MCP adapter, without duplicated authority or orchestration;
- Spring Boot remains the desktop composition root with the narrow DEC-0060 local MCP HTTP exception; Spring Modulith still verifies the JavaFX-free
p.studio.coreboundary; p.studio.Container,AppContainer, and the mixedprometeu-studiomodule are not valid final architecture.
Integrated MCP connection
DEC-0061 revises the baseline with Studio-owned mcp --project mode, grant-time
project discovery, scoped HTTP credentials, one-time scaffold/preparation and a
stable installation with bundled Java. Specs 8–11 define the lifecycle and
transport boundaries; spec 1 defines project creation. PLN-0140 is complete;
automated results and user-confirmed manual acceptance are consolidated in
LSN-0077.
The earlier HTTP evidence was not substituted for these gates. The embedded
terminal remains separate.