The factory floorControl room · agentic engineering era
The dark factory stops for one thing: context.
The lights come on for two things: requirements and taste.
A fleet of coding agents can run from intake to pull request with nobody in the loop. Ours does it by refusing to start on a thin specification, writing an acceptance test per criterion and proving each one fails before the change exists, then handing the model the spec and none of the gates it has to pass. The context is what makes that possible.
What is left for people once agents take the typing is narrow and hard: saying precisely what to build, and judging whether what came back is any good. Kogent builds the instruments for those two jobs, at the speed a fleet runs.
Lights off · the line is runningLights on · the line is waiting on you
The shiftThe bottleneck
Software production is going dark.
The bottleneck moved off the keyboard.
Fleets of coding agents now write, test, review, and ship around the clock while people move from the line to the control room. That's the dark factory pattern. It usually breaks somewhere less interesting than the tooling: the run reaches a question the specification never answered, and there is nobody on the floor to answer it.
The answers almost always exist somewhere. They're in one engineer's head, or in a chat thread from March that nobody exports, or in the corner of the domain that only the person who left last spring ever really understood. Each of those gaps surfaces as a question mid-run, and every question turns the lights back on.
Agents write, test, and review faster than a team can read the output. Delivery has barely moved, because the work that actually gates a release sits on either side of the keyboard: deciding precisely what to build, and working out what to make of what came back.
A gate can prove a change matches its specification. No gate can tell you the specification was worth writing, or that the result is any good. That judgement stays with you. Lights that come on because a question went unanswered are a failure. Lights on because it is your turn are the design.
What we buildWhere you come in
This is the half that runs without you. This is the half that needs you.
Context supply
Everything the factory needs to know
Intent, decisions, constraints and domain knowledge, captured once and kept current in a form an agent reads without asking anyone. Each item stays traceable to where it came from, so a run that leans on a decision can cite it.
Verification
Proof the change matches the spec, before anyone looks
An acceptance test per criterion, authored before the change and proven to fail against the untouched repository. The model that writes the change never sees them. Anything touching tests, CI configuration or a lockfile is routed to a person.
Unattended operation
It runs dark until it needs you
Intake, generation, verification and repair proceed with nobody in the loop. The run stops at the review gate and waits there. A pull request opens once someone has approved the review and the run's own verdict is a pass.
Requirements
Say what to build, precisely enough
Your intent becomes a specification with criteria a machine can hold you to. A spec that is empty, below the completeness threshold, or carrying no testable criteria is refused before a run starts. The refusal is code, not a model's opinion of your work.
Product direction
Decide before the first agent runs
A release brief built from research: personas, trade-offs and journey maps, each one traceable back to the interview or document it came from. You settle what is worth building while changing your mind is still cheap.
Knowledge work
The record the factory reads and writes
Decisions, domain knowledge and the documents that carry them, kept as durable artifacts rather than chat history. Every run is stored as a replayable record and the audit log is hash-chained with signed checkpoints, so the question of why the agent did that still has an answer six months later.
From the founder
Some things the pitch leaves out.
I'm Pratul. I build Kogent and I write this site, so the caveats may as well come from me. Kogent will not make your engineers faster at writing code. Plenty of tools already do that. The work here is the specification going in and the judgement coming out.
One run, 14 July. I pointed the factory at a public fork of the Angular RealWorld app, a codebase nobody here had written, and asked for estimated reading time on articles. Five acceptance criteria. It came back with twenty-four lines in one file, having worked out that the article page and the feed cards share a meta component, and it cleared the repo's own 180 tests in a separate sandbox. I read the diff, approved it, and merged PR #5 forty-two seconds later.
Signature enforcement ships off by default. We are aligned with 21 CFR Part 11 and we are not a validated Part 11 package. The full trust posture, including what is not built, ships as product documentation. Ask and we will send it.
Get in touch
Where does your factory still stop?
What is your factory waiting on you for?
Tell me where your agents stop and wait on a person. I'll tell you which of those gaps context can close, and which ones are going to stay yours.
Tell me where the answer still has to come from a person. I'll tell you what to hand the line instead so it stops asking you.
pratul@kogent.ai