---
title: "2389: The Dark Factory Is a .dot file"
slug: 2389-dark-factory-dot-file-2026-03-09
type: source
created: 2026-06-17
updated: 2026-06-17
status: active
tags:
  - source
  - dot
  - pipeline
  - attractor
  - dark-factory
sources:
  - https://2389.ai/posts/the-dark-factory-is-a-dot-file/
related:
  - dot-pipeline
  - attractor-pattern
  - agentic-pipeline-runner
  - tool-nodes-vs-llm-nodes
confidence: high
contradictions:
  - The post says the factory code is disposable, but its examples also show substantial runner architecture and validation behavior that must be implemented carefully.
bead_refs:
  - dark-factory-rr4
---

# 2389: The Dark Factory Is a .dot file

Source URL: [2389 Research post](https://2389.ai/posts/the-dark-factory-is-a-dot-file/)

Published: 2026-03-09. Captured: 2026-06-17. Provenance: primary blog post by Harper Reed describing DOT pipelines, Attractor convergence, and 2389 runner implementations.

## Compact Takeaways

- StrongDM's Attractor NLSpecs describe three layers: unified LLM client, coding agent loop, and DOT-based pipeline engine.
- Independent implementations such as Kilroy, Mammoth, Smasher, and Tracker converged on the same three-layer architecture, which the post calls the [[attractor-pattern]].
- The reusable factory artifact is the [[dot-pipeline]]: a Graphviz DOT graph describing workflow stages, LLM calls, human gates, forks, and verification commands.
- The post favors deterministic tool nodes for setup, validation, and deployment, reserving LLM nodes for work that genuinely needs model reasoning.
- Complex pipelines can encode the entire software development lifecycle, including human gates, TDD loops, retries, multi-model review, and shipping decisions.

## Wiki Implications

- [[tool-nodes-vs-llm-nodes]] should be treated as a design axis for cost, reproducibility, and operational confidence.
- [[specs-vs-code]] should distinguish disposable generated runner code from durable pipeline blueprints.
- [[how-do-dot-pipelines-map-to-agent-workflows]] should use DOT as a process definition, not merely a visualization format.

## Caveats

- This source mixes product narrative, implementation notes, and advocacy. Treat claims about what is "the product" as a position, not a settled industry standard.
- The post says pipelines are the durable artifact, while [[dan-shapiro-you-dont-write-code-2026-02-13]] emphasizes validation systems and factory operation.