AGENT FACTORY · HOW WE RUN IT IN-HOUSE
Built by agents.
Approved by people.
Governed by rules.
OSOL’s governed way of building software with AI agents: every change starts from an approved request, passes four human decisions and is checked automatically before it is accepted. The same discipline runs our production pilots in your plant.
- 11
- specialist agents, one job each
- 4
- human approval points on every change
- 8
- automatic checks, plus an optional AI review
- ~17 min
- of agent work on our pilot feature, plus human review
From a word in a table
to machine health at a glance.
One request from a maintenance planner: “Let me see the health of every machine at a glance.” Same plant data, before and after one run of the factory.
Plant summary, one card per machine, the reason in words. Illustrative case · synthetic data.
| ID | NAME | TYPE | SITE | STATUS |
|---|---|---|---|---|
| B-401 | Steam Boiler | Steam boiler | Plant A | Critical |
| C-204 | Air Compressor | Air compressor | Plant B | Warning |
| P-102 | Pump | Pump | Plant A | Warning |
| P-101 | Pump | Pump | Plant C | OK |
| M-310 | Conveyor Motor | Conveyor motor | Plant B | OK |
| K-512 | Packaging Conveyor | Packaging conveyor | Plant C | OK |
Status is a word in a table. Illustrative case · synthetic data.
One feature, request to acceptance,
four decisions by people.
A coordinating agent hands each step to the right specialist, records every result, and pauses whenever a person must decide.
- Presenter
The request
A request arrives in plain words: “Let me see the health of every machine at a glance.”
- EngineerProduct Manager
Story and AP1
The research agent maps what the change touches. The story agent writes the story and acceptance criteria. The run pauses for the Product Manager.
Use the feature-factory skill to run the factory on issue #3. - EngineerTech Lead
Technical brief and AP2
A one-page brief with a test for every criterion. The run pauses for the Tech Lead. No code is written before this point.
Continue issue #3 - Agents
Build, test, validate
Build agents write the code and tests. The test agent proves every criterion. The validation agent checks scope and security. The change is prepared for review.
Continue issue #3 - EngineerPipeline
Engineer review · AP3
An engineer reviews every changed line and confirms the AI disclosure. Automatic checks verify the approvals, protected files and secrets, then hold the change for a second reviewer.
/ready - ReviewerEngineer
AP4 and acceptance
A reviewer who is not the author approves. All checks pass and the change is accepted.
Whatever the agent is told,
the controls hold.
Four attempts, four refusals. Each one runs live as you scroll.
Add a package
Refused before it runs. A person decides.
Weaken a control
Refused. The pipeline and its safety rules are protected.
Fake an approval
Refused. Approvals are checked against their full history; only named approvers count.
Change the story after approval
Refused. A changed story needs a fresh approval before the change is accepted.
See the factory
run on your use case.
Bring one real request. We will show you every step, every decision and every check.