The OS
The shell. Identity, files, models, memory, themes, permissions, automations. What every Space inherits.
Product
How Construct is put together.
Six layers, one product. The OS at the bottom, Spaces on top, Operator inside each one, Morpheus watching, marketplace distributing, SDK keeping it open.
Screenshot needed
Isometric exploded diagram of the Construct product, top to bottom: Spaces (UI tiles), Operator (panel), Morpheus (loop arrows around the operator), Marketplace (rail of Space cards), SDK (terminal + code snippet), OS (slim base layer with identity, files, models, memory, permissions). Thin dotted lines + small labels on each layer. Same visual language as anatomy-of-a-space.png so the two read as a set.
/shots/product-layers.pngLayers
Top to bottom.
Spaces
Installable surfaces — one per workflow. Each owns its UI, data model, actions, and Operator persona.
Operator
The AI inside each Space. Specialists, multi-model, multimodal, with explicit autonomy controls.
Morpheus
The autonomous mode. Watches sessions, scores agents, fixes weak prompts, persists what works.
Marketplace
Where Spaces live. Public catalog, private to your org, or scoped to a project — same SDK either way.
SDK + CLI
Vue 3 plugins, six platform APIs, scaffold-build-publish in minutes.