Why Camelia specializes to the page you're on (Design, IDE, Canvas)
Camelia adapts to wherever you're working. A "page surface" layer changes which tools she prioritizes and how she acts, so the same copilot becomes a CAD assistant, a code editor, or a flow-builder depending on the section you're in.
Design Studio
On the Design Studio surface, Camelia can update the live model directly. She replaces the live Cascade Studio script via a special directive, which costs nothing and is prioritized over her archived-CAD tools. This lets you iterate on what's on screen in real time rather than kicking off a separate generation.
Software IDE
On the Software IDE surface, Camelia edits the very Documents files you see in the editor. Because the IDE works over your project's full Documents folder, her edits land in the same files you're reading and saving — no separate copy, no drift.
Project Canvas
On the project Canvas, Camelia can wire dependencies into flows and artifacts. She emits a wiring directive and the canvas draws the connection, turning your visual workspace into something she can actively assemble.
Why this matters
Specializing to the page does two things. First, it makes her more accurate: she reaches for the right tool for what's in front of you instead of a generic one. Second, it keeps her actions in context — edits on the IDE touch your real files, design changes update the live model, and canvas wiring builds the graph you're looking at.
Underneath, it's the same Camelia with the same grounding and the same safety gates; only the prioritized toolset shifts. So you can move between Design, the IDE, and the Canvas and trust she'll behave appropriately for each.