Software that ships with every engagement
The platform comes with the team.
Every engagement ships with working software, not just people. Tuned to your stack, and the source is yours to keep.
Full per-tool detail at r90.ai01 · Architecture
It’s not a suite of apps. It’s a stack.
The platform isn’t a set of tools you log into separately. It’s three layers that build on each other.
Canon, the context layer, holds everything the work knows: PRDs, ADRs, research, and decisions, imported from your repo and queryable in plain language. Habitat, the workflow layer, runs on top of it, across the SDLC. Olympus, the agent plane, puts agents to work inside that same workflow, reading the same context.
Each layer makes the next one stronger. An Olympus agent acts on a spec in Habitat, grounded in context from Canon it never had to ask anyone for. That’s why the platform compounds instead of fragmenting. The alternative, tools with private memory, doesn’t compound. It splinters.
02 · Habitat · Workflow
One source of truth, from the first discovery call to production.
Workflow management across the software development lifecycle, built on Canon so every stage reads from the same memory.
Habitat sits on Canon, the context layer: your PRDs, decisions, and research, imported from the repo and queryable in plain language. RAG chat against the full corpus means every stage of the workflow reads from context instead of interrupting someone.
Plan, build, and verify in one place. Every work unit carries its own verification criteria, and every decision traces back to the context that produced it.
Full Habitat detail at r90.ai03 · Olympus · Agent plane
Agents that do the work, under your governance, in full view.
Olympus is where agents run. Not one assistant, but teams of them, each built for a class of work, running autonomously in a harness you can see into and control. They work inside Habitat, against your context, and every move is visible and governed.
Governed autonomy, not a black box.
Every agent in Olympus runs where you can watch it: its thinking, its current state, its token usage, all in view. Build and extend with custom agents and teams for your own workflows. Nothing runs that you can’t see, pause, or audit.
04 · The wider bench
And a deep bench, for the work that asks for it.
Beyond Habitat and Olympus, we keep a long list of individual tools and agents, deployed when the work calls for them, not before.
The bench grows with the practice. What proves out in client work becomes a tool the next engagement can reach for.
05 · Licensing & ownership
You keep the source. For good.
Every tool we deploy on your engagement comes with a perpetual license to its source code. Run it, change it, fork it, host it yourself. It stays yours whether or not we’re still working together.
The license covers the tools that touched your work, for use inside your business. You can’t resell or redistribute them. Short of that, the code is yours to do with as you like, on your own infrastructure and model contracts. No per-seat metering. No expiry.
Ownership comes with the engagement and never lapses. Staying current is what an ongoing relationship buys: new agents, new capabilities, and the support to run them. Your version keeps working regardless. The relationship is how it keeps improving.
And everything the platform produced is already yours: the context library in Canon, the work history in Habitat, the agent records and findings from Olympus, all in your repositories. You’re not renting tooling. You own the architecture, and it outlasts us.
Redirect your workflow in 90 days
Ask what ships with your engagement.
Thirty minutes with a principal is usually enough to name the tools that would actually move the needle, and the ones that wouldn’t.