The next stretch
Getting to production is a different job.
You built something real, and it works. Now the codebase has grown past what one person can hold, and every change seems to move something you didn't touch.
After you ship
Your customers find the bugs before you do.
A customer hits the bug before you do. Sometimes they tell you. Sometimes they just leave, and you never learn why. Something breaks and you cannot trace what caused it, so every fix is a guess. You slow down, then stop shipping, because you can no longer tell whether a change is safe.
Production software holds when correctness is something you can check on demand, tests fail the moment something breaks, and you know a change is right before anyone depends on it. When something fails, you see where it happened and how it got there, and the way back to steady is clear. The next person to open the code can read it and change it safely.
ACE at work
ACE brings everything we know to your code.
ACE is the AI coding environment we built for ourselves, one Rust binary. It reads your code with everything we've written down in hand, working through each AI backend we use — Claude, Codex, opencode — and it shows how every decision resolves. Experienced engineers decide what applies to your product. Trust modes govern how much runs unattended, and a human signs off before anything ships.
$ ace --help setup Set up a school (clone + auth + config) skills List or curate the skills active in this repo explain Explain how a skill resolves (provenance + trace) pull Fetch the latest school changes mcp Manage MCP server registrations backend claude · codex · opencode trust default · auto · yolo
What we know
The rules, written down and versioned.
The school is a versioned git repo holding what we've learned as engineers, written down as skills. Any rule traces back to where it came from. Because it's versioned, you can read the rules yourself. A fix found on one job reaches your project too, since every project pulls the same updates.
$ ace setup prod9/school cloning prod9/school … skills linked · provenance verified $ ace status school prod9/school · 10 skills linked · no drift $ ace pull fetching prod9/school … 3 new commits general-coding updated frontend-coding updated p9-brand unchanged craft up to date
- Your project gets features that arrive checked, and stay checked as the code changes.
- Every change leaves its reason behind. Months later, your team can see why it was made.
- When something fails, it fails in the open.
- Replaced code is cleared out, so the code your team reads is the code your product uses.
- A bug we hit once becomes a rule your project inherits.
To production
From finished code to real servers.
Platform is the tool we built to take finished code and stand it up on real servers where your customers can reach it, one Go binary. It reads a project, works out what kind it is, and packages it the same way each time, with no per-project build setup to write.
$ go run platform.prodigy9.co@latest init # scaffold platform.toml + the ./platform launcher $ ./platform build # build the container image locally $ ./platform release -p # cut + push the next release tag $ ./platform publish # build + push the image for the release
Show us where it stalled.
Send us the codebase and tell us where it stopped moving. We'll read it and tell you straight what it will take.