Thanks! Great question. We see canvases as living workspaces, you can revisit, iterate on, and build on them over time.
But the deliverables (docs, slides, code) are first-class outputs you can export and use independently. So it works both ways depending on the workflow.
Kavla looks cool, canvas-based SQL is a great use case for this kind of thinking!
But the deliverables (docs, slides, code) are first-class outputs you can export and use independently. So it works both ways depending on the workflow.
Kavla looks cool, canvas-based SQL is a great use case for this kind of thinking!