Not a DevOps tool
We sit in front of DevOps Center, Gearset or Copado. They move and test metadata. The harness decides who may build, who must review, and when a person presses go.
How it works
No magic and no black box. Seven steps, in the order they run, with the files and checks each one leaves behind. Everything here is installed in your own accounts and stays there after we leave.
Salesforce sandboxes and production, GitHub, your AI subscriptions: all of it stays in your name. We never hold production credentials. The access we get is read-only and time-boxed, and it is revoked at handoff.
During the setup we work from an invite you can withdraw at any moment. Production is never on the list.
It starts from a written brief that names the files it may touch and the tests it must pass. The builder works in a branch, never on main, never in production. A file the brief did not name is out of bounds, and the reviewers check for exactly that.
The brief is a plain text file in your repo. A person writes it; it is the contract the review is judged against.
Two reviewers from different model families each read the same commit, not a summary of it. Each writes a verdict file: GO, GO-WITH-CHANGES or NO-GO, a findings list, and the hash of the tree it reviewed. The builder never reviews its own build.
A verdict without a tree hash is not a verdict. The hash is what ties the review to the bytes.
A script, not a person, reads the verdicts. It releases only when two different reviewers passed the same hash, and that hash equals the tree about to deploy, right now. Edit one line after review and it refuses. Reuse an old verdict and it refuses.
The gate's seven refusals are listed on the playbook page, and the free Release Pack includes the script.
A check-only validation runs in the target org and deploys nothing. A person reads the result and presses go, in writing, for this exact release. The validated job is then deployed as-is; no fresh package is built. A post-deploy check confirms the feature is actually on.
Pressing go is a rule the team follows, not something the script can do. We say so because it matters.
Rules, lessons and org facts live as plain files in your repo. Every agent reads them before it works. A lesson written once, by anyone, applies to all agents from then on. There is no second copy to drift.
Teach one agent, every agent learns. A correction becomes a line in a file, and the next run reads the file.
Each person on the team has a daily spend limit on the AI plans your company holds. The limit is checked before each model call, not after the bill arrives. When it is reached, the call does not go out and the person is told why.
Costs land on your own AI plans and vary with usage. The limit is the thing that keeps a bad day small.
The gate, in full
What can still go wrong
What we are not
We sit in front of DevOps Center, Gearset or Copado. They move and test metadata. The harness decides who may build, who must review, and when a person presses go.
We never hold production credentials. Nothing automated reaches production, during the setup or after it.
Nothing runs on our servers. The scripts, skills and memory files live in your repo and run in your accounts.
No subscription, no usage fee, no minimum. After handoff you owe us nothing unless you book an advice session.
What you own on day one
After handoff your team owns every script, prompt, skill, rule and memory file, in your repo, under your accounts. We keep no copy. You get a written deletion confirmation from us within seven days.
The audit tells you which of these steps your team is missing, in writing, within 48 hours. A question gets a plain answer from a person.