Layer 1
Intake
From a form to a plan
A request comes in. The agents turn it into a plan a person can check.
How it works
AI does the work. An engineer signs off.
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.
- Every
- client email with AI in it is read by a person before it sends
- None
- of our sites goes live until a person pushes it
- Nightly
- security sweep across our sites and services
The pipeline
Four layers. A person at the end.
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.
- Agents do the work
- Rules and sign-off
- Feedback loop: Layers 3 and 4 back to Layer 2
Hands off: Draft proposal and dossier
Layer 2
The Pipeline
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
The Specialists
One job per agent
Each agent does one kind of work, and other agents check it.
Hands off: Work ready for review
Layer 4
Sign-Off and Delivery
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.
See it run
Start a job and watch it move.
Each dot is a piece of work. Agents do the work, and every dot stops at a person before it reaches you. Pick a job below, then play both sides: approve it as the person, and answer it as the client. Colors run red to violet, in the order the work moves.
Scroll sideways to see the whole board.
Try it
Getting started
Your build
After launch
- Work moving
- Approved, paid or live
- Sent back to be fixed
Waiting on a decision
Nothing is waiting. Pick a job to start one.
Sign-Off and Delivery
A Person Approves
Human sign-off
A person approves every proposal, reply, preview and launch. Nothing reaches you or goes live before that.
Select any box on the board to read what it does.
Straight answers
The questions people ask before they trust a build like this.
Short answers. Each one maps to a box above, so you can check the claim against the box that does the job.
No. A build stops at a preview. A site goes live when a person pushes it from source control. Social posts and client emails work the same way: each one is approved by hand first.
Your project
Same pipeline, your business at the top of it.
The intake form is Layer 1. Fill it in, and the first thing you get back is a scoped plan an engineer has read.