What is a dark factory in software development?
A dark factory is a metaphor for highly automated software delivery in which agents implement work from specifications and feedback. It is not a universally defined maturity standard. The useful question is which decisions can be delegated while requirements, evaluation, and operational accountability remain explicit.
What does the source say?
StrongDM describes its software factory as non-interactive development driven by specifications and scenarios. That is a team’s reported approach, not a general guarantee of safe autonomous delivery.
How can you apply this?
Choose a small internal tool with reversible changes. Write two desired behaviors, one unacceptable behavior, and a release-stopping condition before asking an agent to implement it. Keep the acceptance scenarios separate from the implementation instructions. Review the resulting behavior and document who can halt or roll back the release. Ask who independently checks the acceptance scenarios and how a customer-visible defect would be detected after release.
What should you watch out for?
Removing code review does not remove responsibility. A green test suite can miss an incorrect business assumption, a security boundary, or a scenario that nobody specified.