Canvas And Documents
10 articles
Using the Canvas: where flows, renders, and docs land together
The project Canvas is the visual home for a single build, where imported repos, flows, renders, and docs converge and Camelia can wire dependencies together.
The Documents folder backbone and the nine project folders
Documents is the project's encrypted backbone of fixed folders stored in Cloudflare D1; key folders like Flows, Design, and Outputs also drive project progress.
Uploading files with drag-and-drop (and how they're encrypted)
Drag files onto the Documents dropzone (or browse) to upload into the open folder; everything is AES-GCM encrypted at rest with a server-only key.
Smart labels: how files get tagged and how to relabel them
Smart labels (Research, Spec, Design, Legal, Finance, Manufacturing, Marketing, Misc) tag every file; set them yourself or let Camelia's Smart Label run tag unlabelled files.
Viewing, editing, moving, and deleting files in the Documents browser
View, inline-edit, move, and delete files from the Documents browser; saves create a new encrypted version, and Camelia-proposed deletions require your approval.
Navigating nested folders from imported repositories
Imported repos clone into Documents with their directory structure intact; the browser reconstructs the tree from slashed file keys so you can descend folder by folder.
Using 'Organize' to dedupe, flag conflicts, and move misfiled files
Organize hands your whole project to Camelia to dedupe, flag conflicts, label every file, and refile misplaced docs — with any deletion gated behind your approval.
Using 'Smart Label' to tag only your unlabelled files
Smart Label asks Camelia to tag only your unlabelled files, choosing the best label for each while leaving already-labelled files and folder placement untouched.
How project progress is derived from which folders have content
Progress runs through five phases — Idea, Intention, Project, Invention, Product — each completed by content in Documents, Flows, Design, or Outputs; never hardcoded.
Where designs, flow runs, and bundles get saved automatically
Designs archive to Design (GLB/STEP/STL), flow run records and step artifacts save to Flows, and packaged deliverables build into Outputs — all automatically.