Workspace overview

The workspace is organized as a sequence of connected editing contexts rather than a collection of isolated forms. Information entered in one tab becomes context or structure in another.

A recommended working order

1. Define the product description, roles, and features in Domain.
2. Model entities and shared types in Data.
3. Plan routes, components, state, and navigation in Structure.
4. Define or generate the API surface in Backend.
5. Review access in Security and coverage in Traceability.
6. Set the visual system in Theme and project-wide concerns in Misc.
7. Use Export to inspect the resulting file tree and create a report.

You do not have to finish a tab before moving on. The workspace autosaves project decisions, and downstream tabs read the current state. Returning to Domain to add a role, for example, updates the role choices used by Structure and Security.

Tabs and panels

Top-level tabs switch the whole editing context. Some tabs contain a secondary panel list—for example, Domain separates Roles from Features, while Data separates the ER diagram from reusable Types. Canvas-oriented tabs use the full width and keep their own inspectors and tools.

The save indicator in the workspace header reports whether the project is saved, saving, or in conflict. Only project owners can currently persist workspace changes; other members see a view-only warning.