Project Workspaces
A workspace should correspond to one unit, study, or delivery phase. It binds session context, files, memory, knowledge, and approved capability settings to the engineering object under review.
Workspace design
01Name the object
Include the unit, objective, and phase in the workspace name.
02Control revisions
Identify superseded material before it can influence conclusions.
03Separate alternatives
Keep incompatible design cases in distinct milestones or workspaces.
04Preserve decisions
Archive the inputs, assumptions, approval, and selected result behind an important decision.
Session binding
One session, one active workspace
The active session is bound to a workspace path. Switching sessions does not silently merge project material or running task streams.
Data policy
Use authorized data only
Do not place credentials, license files, unapproved customer material, or unrelated project data in a workspace.