Spaces Pipelines

Tasks use the states pending, assigned, in_progress, completed, and error. Individual runs use queued, streaming, completed, error, and cancelled. These visible records make it clear what happened to each task and run.

Pipeline output first appears as a result for review. The result controls are Review, Apply, Create Doc, and Copy. Review creates a follow-up review task for the result; Apply writes the result into a linked document; Create Doc makes a new native document; and Copy copies the output.

Completing a run never silently changes a linked document. A result remains a proposal until you choose an apply action.

Each task can draw on the Space’s shared context, its linked documents, resolved document mentions, and prior task outputs. Treat this as a bounded context bundle: the material selected for the Space and task, not permission to search every document by default.

Spaces are owner-scoped. The owner controls the Space, its agents, shared context, and linked documents; tasks and runs are checked against that ownership. Keep external or sensitive material out of shared context or linked documents unless it is approved for that Space.

A result is a proposal until a writer applies it. This review boundary makes it possible to inspect an agent's work before it changes a document.

Immediately before a result is applied to a linked document, Skraib creates a version checkpoint of that document’s current contents. The checkpoint preserves the before-apply state so the change has a clear recovery point.

Explore Spaces for the product workflow and guardrails, or explore IWE for drafting and branch workflows.