Workspace

The workspace is the project-level entry point. It helps you answer three questions: what products exist, where each one is in its lifecycle, and what action is safe to take next.

Projects, not generated folders

A project is the durable container for:

• the current Evolutionary Model;
• immutable prior revisions;
• discovery and design conversations;
• validation and readiness state;
• generated artifacts and previews;
• delivery records where managed delivery is enabled.

The generated folder is an output of a project revision, not the project itself.

Lifecycle stages

A project normally moves through:

1. Discover — establish the problem, domain, actors, rules, and constraints.
2. Design — resolve experience, views, navigation, and visual intent.
3. Generate — validate and compile the revision.
4. Preview — run the candidate and test real journeys.
5. Deliver — export, hand off, or promote an approved release.

These are not irreversible wizard steps. You may return to discovery or design whenever a product decision changes. The revision history preserves what produced each candidate.

Project status

Status should describe evidence, not activity. Useful distinctions include:

• a model is still being discovered;
• the structural readiness gate is blocked;
• an experience blueprint is missing or stale;
• a candidate is generating;
• a preview is ready or failed;
• a release is active, superseded, or rolled back.

Avoid interpreting “generated” as “production ready.” Generation proves that the compiler accepted the input; promotion requires deployment and verification evidence.

Naming and descriptions

Choose a product name that identifies the business capability, then use the description for the measurable outcome. Good descriptions help discovery distinguish product intent from implementation preferences.

Name: Clinic Scheduling
Outcome: Coordinate appointment requests and confirmations while preserving
         patient privacy and preventing double booking.

Leaving and returning

The model, discovery state, and revisions are persisted with the project. When you return, continue from the current project state rather than restating the entire brief. If the model changed since the last design pass, modelARch should mark derived experience artifacts as stale and request a targeted refresh.

Continue with Discover or learn how Projects and revisions preserve history.