
How we work
You want your project built well, whichever day it gets touched and whoever touches it. Our engineering standards are wired into every AI session we run, so the quality holds.
01 — The tool
ACE is the AI coding environment we built for ourselves — one Rust binary. It carries our versioned standards into each AI backend we use, Claude or Codex or opencode, and shows how every decision resolves. Trust modes govern how much runs unattended; 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

02 — The knowledge
The school is a versioned git repo holding what we've learned as engineers, written down as skills. Any rule traces back to its source, so nothing is folklore. Projects link to the school and pull updates, so a fix found on one job improves the standard for yours too.
Behind the link is a written standard of hard rules, and they hold even when the deadline is tight. When your project points at it, your code inherits them.
$ 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

Send us the problem and we'll say straight whether we can help. You'll be talking to the engineers who'd build it.