Apps & Interfaces · 07.08
Artifacts: The Product Library
Persisted, referenceable artifacts collected for delivery, with retention policy and a dedicated library surface.
What a run actually produces, kept and referenceable
The artifact_save and artifact_collect workflow nodes persist a run's real deliverables — a generated document, a report, a rendered file — as referenceable objects rather than transient node output that vanishes once the run settles. A dedicated Artifacts library surface makes them browsable after the fact, and a retention policy governs how long they stick around, so the platform doesn't have to choose between keeping everything forever and losing delivered work the moment a run's context is gone.
Continue
Workflow package CRUD and install-from-local-manifest — reusing a proven graph instead of building one from scratch.
A surface is a typed ViewNode tree — layout, data-bound views, interactions, and agent-native widgets an agent can render, patch, and lint safely.