Interactive profile surface
A real product where professional profiles are readable by humans and useful to agents.
Governance is not process. It is survival.
Software Dark Factory comes from 20+ years of owning startup software from idea to production - and from turning that lived governance discipline into a product for agentic engineering.
Software Dark Factory exists because AI-assisted delivery has made an old startup problem more urgent: teams can now produce work faster than they can confidently review, govern, and trust it. The model was not born from a governance framework. It came from the reality of owning software delivery end to end in startups: clarifying ambiguous ideas, building in small implementation steps, testing, deploying, watching production, maintaining systems, and carrying the consequences when things break.
This memo exists to explain the lived operating experience behind the product: why the journey starts with a readiness snapshot, why deeper assessment needs evidence, and why speed only matters if it remains reviewable.
Founder-market fit
Built from full-SDLC responsibility.
For more than 20 years, I have worked in startup environments where the same person often has to move from founder idea to specification, implementation, testing, UAT, deployment, production support, maintenance, and scaling.
The playbooks behind Software Dark Factory were not created as content. They were extracted from years of running software delivery under pressure: solo ownership, small teams, production systems, AI-assisted workflows, and the need to move faster without lowering quality.
The most dangerous failures were rarely obvious syntax errors. They were changes that crossed hidden business boundaries: pricing, fulfilment, access, commercial commitments, ownership, operational support, or customer trust.
In that context, governance is not process overhead. It is how teams preserve control as delivery accelerates: keeping intent, risk, evidence, and verification attached to the work.
Why now
Agents make the old discipline explicit.
Experienced engineers already know that loose briefs create expensive downstream problems. Agentic development makes that more visible.
The executor is faster now, but delivery has not become simpler. Faster code generation only helps when the brief, boundary, verification, evidence, and review still travel with the work. Agents should strengthen that workflow, not bypass it.
Software Dark Factory starts with foundations serious SDLC already depends on: clear scope, reviewable changes, verification evidence, risk management, proven design patterns, and disciplined delivery. The difference is that those foundations now need to work with agents in the loop.
A faster way to produce code is not the same as a faster way to deliver software.
Origin proof
Explore was the agent-first proof ground.
Explore is the live product where this work started: an interactive professional profile designed to be readable by people and usable by agents.
It proved the agent-first direction in a real Rails product: agent-accessible profiles, browser-light setup, and workflows that needed clear state, approval, evidence, and boundaries.
Software Dark Factory is the governance product path extracted from that work. Explore proved the agent-first surface; Software Dark Factory productizes the delivery governance needed to make agentic engineering safe and repeatable.
What Explore proved
Agent-first workflow
Guided setup and browser-light approval showed how products can be designed for agents as first-class users.
Governance extraction
The delivery workflow around Explore shaped the Software Dark Factory model: intent, evidence, checks, review, and approval before work moves forward.
Assessment wedge
Why assessment comes first.
Most teams should not jump straight from AI coding tools to autonomous delivery. The first question is whether the repo is ready: tests, CI, review flow, evidence discipline, boundaries, and deployment confidence.
That is why Software Dark Factory starts with a free repo-backed readiness snapshot, then moves qualified teams into a paid evidence-backed readiness assessment when more depth is useful.
From there, assisted governed front door setup creates the first controlled work item. The operating layer that follows should fit the actual repo, team, review process, stack, and risk profile.
free repo-backed readiness snapshot
paid evidence-backed readiness assessment
assisted governed front door setup
customer-specific operating layer
Operating thesis
The goal is controlled speed.
The goal is not uncontrolled automation. It is controlled speed: agentic work entering the repo through a governed front door with intent, evidence, checks, review, and approval attached.
The same playbook-led approach has been used in real delivery environments to make work smaller, more reviewable, and more regular without treating speed as a substitute for quality.
That is why this is not another AI wrapper. The product path is governance infrastructure for teams that want agentic engineering speed without losing operational control.
Practical starting point
If this resonates, start with the repo in front of you.
If this resonates, the practical starting point is not a platform install or a big transformation programme.
It is a free repo-backed readiness snapshot: whether your repo appears to be a fit, what lightweight signals are visible, and whether a paid evidence-backed assessment is worth the next conversation.
The aim is a working rhythm where AI can help produce software, but the team still owns the brief, the evidence, the review, and the decision.
Related writing
Original source.
When you own the full SDLC alone, governance is not process. It is survival.
The full essay expands on the full-SDLC ownership story behind this founder memo.
Read the full essay: "When you own the full SDLC alone, governance is not process. It is survival."I am not dropping twenty years of delivery practice for agentic speed
The full essay expands on the full-SDLC ownership story behind this founder memo.
Read the full essay: "I am not dropping twenty years of delivery practice for agentic speed"Proof and profiles
Follow the work.
Follow the founder's work on agentic engineering, full-SDLC governance, and Software Dark Factory.