Using the Canvas: where flows, renders, and docs land together
The project Canvas is where your work comes together visually. When you create a project and pick a path, you land inside that project's Canvas (/<projectId>/canvas), the spatial home for your build.
What lives on the Canvas
The Canvas is the visual workspace for a single project. Imported repositories render as one collapsible, connectable "dependency" stack rather than a card per file, so a cloned codebase stays tidy. You can draw your own connections between items, and Camelia can wire dependencies into flows or artifacts on your behalf.
Camelia can act on the Canvas
Camelia, the per-user AI copilot, specializes to the page she's on. On the project Canvas she can wire dependencies into flows and artifacts using a connection directive, so a chat instruction can reshape the graph you see.
How progress shows up
Project progress is modeled as five phases — Idea, Intention, Project, Invention, and Product — and completion is derived from which backbone folders actually have content, never hardcoded. As documents, flows, designs, and bundles accumulate in their folders, the progress reflected across the project updates to match real artifacts.
Where things get saved
Work you generate doesn't stay trapped in chat. Designs and CAD outputs save into the Design folder, flow run records save into the Flows folder, and packaged bundles land in Outputs. The Canvas, Documents browser, and the per-section views all read from this same encrypted project store, so what you see in one place stays consistent everywhere.