Dark Factory category
Where Dark Factory sits
Dark Factory sits below individual coding tools and above isolated internal process. It is the governed delivery layer that connects scoped intent, agent execution, validation evidence, and retained operating memory.
This page is intentionally compact for now: enough to frame the category, without pretending the full competitive memo is finished.
Current status
Route and narrative shell are now in place. A fuller competitive matrix can land later without changing the hub structure.
Exports
Web-first pages now, page-level PDF actions today, combined-pack support later.
Landscape
Four nearby categories, one different job
Coding tools
They accelerate generation.
Dark Factory is concerned with what happens after generation: scope, governance, validation, and the trust boundary around shipping.
Review and governance layers
They often address one bottleneck at a time.
Dark Factory aims at the operating layer underneath them, where jobs, checks, run logs, and release ownership are coordinated as one system.
Consultancies
They deliver work, but do not become the productized operating memory.
Dark Factory is positioned as a reusable kernel, not just a services wrapper around agent assistance.
Internal workflows
Teams build pieces of this themselves.
The opportunity is to turn scattered internal discipline into a clearer, repeatable system with visible proof and a path to reuse across environments.
Memo status
This is a prepared shell, not the final category memo.
The route, navigation, and framing now exist as part of the investor hub. The next slice can deepen this page with more explicit comparison language, market-map visuals, or sharper competitive claims once the content is finalized.