glossary · The process

Workflow fragment

definition

A workflow fragment is a reusable block of steps written once and embedded in many workflows, so a change to the fragment reaches every workflow that uses it.

in one line: Shared steps written once, embedded in many workflows.

in context

Where does a workflow fragment fit?

Edit once. Every workflow changes. In ConvOps, one block of steps, such as a claims check or build and verify, embedded where it is needed.

claims-checkwritten once
Product pageembeds it
Newsletterembeds it
One fragment, many workflows. Example: regulated enterprise content.
two ways to say it

What is a workflow fragment, in plain words?

Same idea at two depths: the plain version, then what the engine actually does.

Copies drift. A fragment keeps a common block of steps in one place.

Embed a fragment for steps that always run. Invoke it from a decision for work that only sometimes happens.

for engineers

A step entry embeds a fragment by name, or a decision invokes it as a child workflow. Fragments are resolved when the workflow is read.

Workspace globals add steps to every workflow. Fragments are unlimited on every plan.

the longer answer

Why does a workflow fragment matter?

Most organizations have steps that appear in many processes: find the standards that apply, build and verify, run a review, capture what was learned. When each workflow carries its own copy, the copies drift. One team adds a lint step, another does not, and six months later "the review step" means five different things. Fragments solve the same problem functions solve in code: write it once, call it everywhere. The same pattern holds outside engineering: a legal check or a brand review used by many content workflows.

A fragment is not a sub-workflow. A sub-workflow is a detour a decision starts at run time, with its own instance and a parent that waits. A fragment is inlined into the workflow that embeds it; its steps simply become part of the line. Use a fragment for steps that always run in that position, and a sub-workflow for work that only happens on some paths.

The design discipline is to keep fragments narrow and outcome-shaped. A fragment called build-and-verify with three clear steps reuses cleanly. A fragment that tries to cover every variant of a process becomes a second monolith.

in convops

How does a workflow fragment work in ConvOps?

In ConvOps, a workflow lists steps, and an entry can embed a fragment by name. Fragments are resolved when the workflow is read, so an edit to a fragment applies to every workflow that embeds it, including runs that reach those steps later. Workspace globals work alongside fragments: they add steps to every workflow, such as a closing step that captures learnings, without editing each template. Fragments are unlimited on every plan, including Free. You create and edit them the same way as workflows, by asking your AI client over MCP. A fragment cannot drift from itself, which is the whole point.

in depth

Embed or invoke: which should you use?

A fragment can be used in two ways. Embedding puts its steps straight into the line of the workflow, so they run on every run, in that position. Invoking starts the fragment as a child workflow from a decision, so it runs only when that branch is chosen, and the parent continues when it finishes. The fragment is the same in both cases; what changes is whether it always runs.

In ConvOps, steps from an embedded fragment cannot be skipped from inside the workflow, and they are edited on the fragment, not on each workflow that embeds it. A fragment can carry its own decisions and fix loops, so a whole review cycle can be one fragment.

Embedding and invoking a ConvOps workflow fragment.
QuestionEmbedInvoke
When does it run?On every run, in its positionOnly when a decision picks that branch
How does it run?Its steps become part of the workflow's lineAs a child workflow; the parent waits and then returns to its line
Can a run skip it?No, not from within the workflowYes, by taking another branch
Where is it edited?On the fragmentOn the fragment
Typical useSteps every run needs, such as a final checkWork only some runs need, such as a legal review on high-risk items
in depth

Which fragments do teams reuse?

The best fragments are short, have one clear outcome, and appear in many workflows. The examples below are typical, each labelled with the kind of team that would own it. In ConvOps, fragments are unlimited on every plan, and workspace globals sit beside them: steps added to every workflow in the workspace, such as a closing step that records what was learned.

  1. Enterprise, regulated content: a medical claims check written once and embedded in twenty content workflows, so a change to the check reaches every one of them.
  2. Enterprise, shared services: a spend approval fragment with a requires_approval gate, embedded in procurement, travel and vendor onboarding workflows across departments.
  3. Content: a review loop with its own decision and fix loop, reused by six workflows, from blog posts to newsletters.
  4. Support: an escalation fragment invoked only when a ticket is marked urgent, so routine tickets never run it.
  5. Software delivery: build and verify, three steps embedded in every workflow that changes code.
in depth

How does one edit reach every workflow?

Reuse only pays if a change lands everywhere without anyone copying it. In ConvOps, fragments are resolved when a workflow is read, not copied into it when it is saved. An edit to the fragment is therefore in every workflow that uses it from that moment, including runs already in progress that reach those steps later. Runs that have already passed the fragment's steps are not changed, because those steps are history.

That property is also the reason to keep fragments narrow. A fragment used by twenty workflows is a change to twenty processes at once. Small fragments with one outcome are quick to reason about. A fragment that tries to cover every variant turns every edit into a negotiation, and becomes the monolith fragments were meant to break up.

questions

What do people ask about a workflow fragment?

What is a workflow fragment in ConvOps?

A workflow fragment in ConvOps is a reusable block of steps written once and used by many workflows, either embedded so it always runs in its position, or invoked from a decision so it runs only on that branch. Because fragments are resolved when a workflow is read, one edit to the fragment reaches every workflow that uses it.

When should I use a workflow fragment?

When the same steps appear in several workflows, such as build and verify, a review loop, a legal check or a spend approval. In ConvOps, write them once as a fragment and embed it, so every workflow runs the same version. If the steps only belong on some paths, invoke the fragment from a decision instead of embedding it.

What is the difference between embedding and invoking a fragment?

Embedding inlines the fragment's steps into the workflow, while invoking starts the fragment as a child workflow from a decision condition. In ConvOps, both use the same fragment, edited in one place. Embedded steps run on every run and cannot be skipped from within; an invoked fragment runs only when that branch is chosen, and the parent waits for it.

Do fragment edits affect workflows that are already running?

Yes, in ConvOps. Fragments are resolved when the workflow is read, so an edit applies to every workflow that embeds the fragment, including runs already in progress that reach those steps later. Steps a run has already completed stay as they were in its history. Keep fragments narrow, since one edit changes every process that uses them.

Are workflow fragments limited by plan?

No. Fragments are unlimited on every ConvOps plan, including Free, and so are the workflows that use them. Workspace globals, steps added to every workflow in the workspace such as a closing step that records what was learned, work alongside fragments. You create and edit both by asking your AI client over MCP.

Which teams reuse workflow fragments?

Teams that run several workflows sharing the same steps, such as a standard review or a release checklist. ConvOps fragments let the workflow owner write those steps once and embed them wherever they apply, so the shared steps are kept in one place rather than copied by hand into each workflow.