dark-factory-buildlisted

# Dark Factory Build — end-to-end orchestrator ## Overview This skill runs a complete Dark Factory build: **intent → semantics → design → tests → code → verification → live proof → shipped + documented.** It is the conductor; the per-stage `df-*` skills do the work. Everything is modeled through the **data-transform lens** (data nodes + pure/effect transforms + validation rules + authority), built **test-first**, **verified adversarially** (never on a self-report), executed **autonomously in dev/non-prod**, and **documented as tickets + DF spec docs + memory** at every step. It is the generalization of a real run: a DEX arbitrage bot taken from half-finished to a liquidity-aware arbitrage engine with 5 DF docs, TDD + ~290k-case adversarial fuzz, and a live on-chain no-overshoot proof — all ticketed and committed. ## When to use - "Build this the dark factory way" / "run a DF build" / "do this end-to-end autonomously." - A spec or half-built project needs to be finished with docs + TDD + verification + tickets. - Any non-trivial feature where you want the full discipline: semantics first, blind-verified, evidence-backed. For a single stage only (just the PO doc, just TDD), invoke that `df-*` skill directly instead. ## The pipeline <!-- ENFORCED. A `PreToolUse` gate (`df-stage-gate.py`) blocks any write to `docs/dark-factory/<NN>-*.md` unless that stage's skill was actually invoked in this session. Writing the artifact from memory is the failure this exists