---
title: Specs vs Code
slug: specs-vs-code
type: comparison
created: 2026-06-17
updated: 2026-06-17
status: active
tags:
  - specs
  - code
  - durable-artifacts
sources:
  - strongdm-attractor-nlspec
  - 2389-dark-factory-dot-file-2026-03-09
  - jleechanorg-dark-factory-repo
related:
  - nlspec
  - dot-pipeline
  - what-is-the-durable-artifact-in-a-dark-factory
confidence: medium-high
contradictions:
  - Treating code as disposable is useful for generated implementations, but production systems still depend on correct executable code at runtime.
bead_refs:
  - dark-factory-rr4
---

# Specs vs Code

Specs describe intent, behavior, process, and validation. Code is the executable artifact produced from those specs. Dark factory sources push the durable boundary toward specs, graphs, tests, and evidence rather than generated code.

## Durable Specs

- NLSpecs define expected behavior and interfaces.
- `spec.md` captures task intent and acceptance criteria.
- DOT graphs encode the development process.
- Holdouts and scoring contracts define validation.

## Disposable Code

Generated code can be rebuilt, replaced, or regenerated. But "disposable" does not mean unimportant. It means the factory should be able to recreate code from durable intent and process artifacts.

## Design Implication

`inference:` The safer framing is not "code does not matter"; it is "code should be reproducible from higher-level durable artifacts and judged by stronger validation."