Work/Blueprints

Blueprints

Reusable definitions of structured Work — Start materializes a task tree; never “Run.”

Blueprints

Blueprints are reusable definitions of structured Work. You Start (materialize) a blueprint into a parent task and plan steps — a fork of the definition, not a puppet of a living template.

Where in the product

Where in the product

Library chrome lives in the Agents dialog (Blueprints page). Domain is Work — materialize into tasks. Routines may also attach a blueprint so each fire starts structured Work.

Agents dialogBlueprintsWork · create / Start

How to use it

  1. Open Agents → Blueprints to browse or author definitions.
  2. Start work from a blueprint when you want a ready plan tree.
  3. Optionally attach a blueprint on a task-routine so scheduled fires mint the same structure.
  4. Edit the live task after start — the instance is yours; later blueprint edits do not rewrite past starts (routines re-read the current definition on each fire when attached).

Key distinctions

  • Verb is Start / Start work — not Run (Run is for agent execution elsewhere).
  • Spine+ here: deep authoring and agent tools stay thin in public docs; product library is SoT.
  • Automations may materialize a blueprint when an event needs structured Work (Work bridge).