How flow steps save labeled artifacts into your project folders
A flow doesn't just produce text on screen — its steps can save real, durable artifacts into your project so the work becomes part of the project's files.
Encrypted, into your project folders
Each step can save its output as an artifact, encrypted, into one of your project's backbone folders. The save is part of the step definition, so a flow can be designed to deposit its deliverables exactly where you want them.
Smart labels
Artifacts are written with a smart label that reflects the kind of work that produced them:
- Role sub-agent steps get labels like Research, Analysis, Design, Spec, Legal, or Manufacturing.
- MCP integration steps are labeled "Integration."
These labels make it easy to scan a folder and understand what each file is without opening it.
How encryption works
Project data — including flow artifacts — is encrypted at rest with AES-GCM, using a per-project key derived from a server-only master key. Keys never reach the browser. This is operator-decryptable encryption at rest (the server decrypts just-in-time to serve you your files); it is not end-to-end or zero-knowledge.
Where they show up
Because artifacts land in your normal project folders, they appear alongside everything else in Documents and Design. A flow that runs a design-and-manufacture sequence, for instance, can leave a design brief, a spec, and a sourcing plan in the right folders. You can also see exactly which artifacts a given run produced by expanding that run in the Runs table.
A note on sourcing artifacts
Manufacturing-step output is an AI-suggested markdown sourcing plan. It's a genuine, labeled artifact — but part numbers in it are suggestions, not catalog-verified or orderable items.