---
title: DOT Pipeline
slug: dot-pipeline
type: concept
created: 2026-06-17
updated: 2026-06-17
status: active
tags:
  - dot
  - pipeline
  - graphviz
  - process-graph
sources:
  - 2389-dark-factory-dot-file-2026-03-09
  - strongdm-attractor-nlspec
  - jleechanorg-dark-factory-repo
related:
  - agentic-pipeline-runner
  - tool-nodes-vs-llm-nodes
  - how-do-dot-pipelines-map-to-agent-workflows
confidence: high
contradictions:
  - DOT is simple and inspectable, but complex software lifecycle graphs can still become hard to reason about without schema validation and visual conventions.
bead_refs:
  - dark-factory-rr4
---

# DOT Pipeline

A DOT pipeline is a Graphviz directed graph used as an executable workflow definition. Nodes represent work, tools, gates, human approvals, joins, exits, or model calls. Edges represent routing, dependencies, retries, success/failure branches, and joins.

## Why DOT

- It is text, versionable, diffable, and visually renderable.
- It can encode both linear and branching workflows.
- It separates the process blueprint from a specific runner implementation.

## Factory Role

In [[dark-factory]], a DOT pipeline can be the durable artifact that records how intent becomes validated software. The runner may change; the graph preserves the development process.

## Implementation Notes

The [[jleechanorg-dark-factory-repo]] uses DOT graphs for task-sized lanes, minimal feature loops, PR review, bug-fix TDD, gates, and benchmarks. The [[strongdm-attractor-nlspec]] defines a generalized DOT runner with typed attributes, handlers, checkpointing, human gates, model stylesheets, validation, and extensibility.