Workspace
The workspace is your account or organization context. It holds settings, durable memory, signed skills, knowledge packs, active chats, notifications, cases, permissions, and the Cases Dock that pins live work across the bottom of the shell. State is reconstructed from typed records, not stored as a synthetic file tree.
Project
A project groups related engineering work — chats, cases, files, runs, approvals, comparisons, reports, and shares. Top-level chat can create or resolve a hidden workspace project on the fly when you start from a template or a plain prompt, so you do not have to create projects first.
Chat
Chat is the planning and coordination surface. It renders typed UIMessage parts — case artifacts, plan updates, tool calls, approvals, logs, failures, and report previews. The renderer never infers simulation state from prose when a typed part exists, so what you see is the same thing the reviewer will see.
Case
A case is the typed simulation artifact. It owns the CaseSpec, workspace files, solver settings, QoIs, runs, validation evidence, and report inputs. Case artifact launchers open the file browser, terminal, viewer, CAD, postprocessor, run timeline, and compare surface — all without losing chat context.
Run and report
A run executes a case through the governed command runtime. It produces logs, residuals, monitors, artifacts, cost, validation signals, and reportable evidence — every record content-addressed. A report packages those records with assumptions, figures, citations, hashes, and review context into a deliverable that another engineer can replay.