Interactive profile surface
A real product where professional profiles are readable by humans and useful to agents.
Founder memo
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 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 slices, 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 assessment starts with evidence, why the workflow is governed, 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.
In that context, governance is not bureaucracy. It is the discipline that keeps software understandable, recoverable, and safe to change.
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, so the brief, boundary, verification, and handoff matter more, not less. Agents did not make governance matter; they made it urgent to make the discipline explicit.
In agentic work, the prompt is the brief. If the brief is unclear, the system inherits the ambiguity.
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, lightweight CLI tooling, 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
CLI-led 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 an assisted repo readiness assessment.
assessment request
safe context sharing
evidence-backed report
implementation path
governed workflow
governed front door
maturity progression
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.
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.
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."Proof and profiles
Follow the work.
Follow the founder's work on agentic engineering, full-SDLC governance, and Software Dark Factory.