Layer 1
Intake
From a form to a plan
A request comes in. The agents turn it into a plan a person can check.
Here’s how a job moves through our shop. AI agents do the research, write the drafts, build the code and run the checks. A person reads the result before any client sees it.
Work flows down. Problems flow back up. Nothing reaches a client or a live site until it clears the checks in Layer 3 and a person in Layer 4. Tap any box to see what goes in and what comes out, plus the rule it runs under.
This is a simple map, not the full wiring. The prompts and the database layout are left out on purpose, along with the exact routing rules. Those are ours.
Layer 1
From a form to a plan
A request comes in. The agents turn it into a plan a person can check.
Hands off: Draft proposal and dossier
Layer 2
Order of work, memory and guard rails
The part that decides what runs next and keeps the record. It also blocks what should never happen on its own.
Hands off: The next step in the job
Layer 3
One job per agent
Each agent does one kind of work, and other agents check it.
Hands off: Work ready for review
Layer 4
A person approves. Then it ships.
Every result a client will see waits here until a person says yes.
Feedback loop. When a check fails, or Matt declines or asks for changes, the job goes back to the pipeline with a note that says why. It runs again from there.
Short answers. Each one maps to a box above, so you can check the claim against the box that does the job.
Your project
The intake form is Layer 1. Fill it in, and the first thing you get back is a scoped plan an engineer has read.