Governed AI development
AGPL-3.0We don't need more AI, we need skills and governance.
AI that follows your rules. Routekit Shell (rks) turns a plain-language idea into scoped, cited, reviewable work — a governed plan → build → ship pipeline with the reasoning attached and the cost visible.
What is Routekit
Not a faster autocomplete. A governed way to think.
rks is skills and governance layered over the model you already use. Instead of hoping the AI does the right thing, every unit of work becomes a story that moves through a real state machine where status is observed, not self-reported.
Scoped
Work is decomposed by concern — one coherent change per story, with the files and acceptance criteria that belong to it named up front.
Cited
Decisions are grounded in your project's own knowledge graph — “here is the note that says so,” not “the AI said so.”
Reviewable
Every gate is inspectable and every transition is recorded — a queryable trail of what shipped and why, for free.
How it works
A pipeline you can watch: plan, build, ship.
Plan
Describe the work in plain language. A product-owner step researches your project and writes a scoped, cited story with testable acceptance criteria.
Build
The story moves through QA and an architectural gate before a line is written. Guardrails redirect risky actions instead of dead-ending them.
Ship
Git is governed and automatic: branch → PR → clean merge, every time, with a full trail behind it. You review outcomes, not diffs you didn’t ask for.
Model economics
Your best model is the fallback, not the default.
Every agent starts small. The expensive one gets used when the work earns it — not before.
Starts cheap
retries before it escalates
Escalates by resuming
not restarting from turn zero
Caches by default
prompt, tools, and turns
Shows the bill
token spend and a waste ratio on every unit of work
Proof by provenance
Routekit builds itself under its own governance.
This isn't a demo that only works on a toy repo. rks develops rks — every feature on this site and the framework itself was planned, gated, built, and shipped through the same pipeline it sells. The strongest evidence that the governance holds is that it holds here.
Every change
is a story with a cited rationale and a state trail.
Every merge
is a governed branch → PR → clean merge.
Every cost
is reported with a spend figure and a waste ratio.
Deep dives
Want to nerd out? Start here.
The team at UX287 has been researching how to build this for a while — here are some of our articles on the thinking behind Routekit Shell.
ux287 · AI-first product & design
Not sure you want the technical weeds? Give us a call.
Routekit Shell is our engine — ux287 is the team behind it. We do AI-first product design, strategy, and delivery: we'll run the governed pipeline for you, turn your idea into shipped software, or help you stand up rks on your own codebase. You bring the vision; we handle the weeds.