Software you can audit. From the spec to the answer.
AI has made building software fast. It has not made it trustworthy. Most of what gets built quickly is built in the dark. We build differently: every stage leaves a record, and the software carries it.
Why this matters more now, not less.
When software took eighteen months, the length of the process was its own assurance. Now it takes days, that assurance is gone. A factory that can’t show what it did hands you software that ages the day its builder moves on. The record is what lets us keep your software right for years. It isn’t paperwork.
The four layers, and what you hold at each.
- 01
The spec is the source of truth.
Outline interviews you, checks what it hears against your data, and writes a numbered spec in plain English. You approve it before any code exists. If code and spec ever disagree, the agent must report it, not work around it.
What you holdThe spec. Plain English, numbered, yours to read, share and approve.
- 02
The build is gated, and the gates are recorded.
We build in tranches, each with a plan, a findings file and a checkpoint, and the next cannot start until the gates pass. Some gates play an attacker against every access rule. Expected answers live in a frozen corpus, so a failing test can’t be quietly edited to pass. A second set of eyes reviews everything before it merges.
What you holdThe plan, and findings as each tranche closes. Progress by what passed, not what was promised.
- 03
The platform is secure by construction.
Everything we build runs on one identity, tenancy and audit layer. Row-level security is enforced in the database, with tests that block a release if it slips. Every read, including the refused ones, writes a hash-chained audit row. Assessed against SOC 2 criteria before any customer data touched it.
What you holdAn audit trail you can export and verify, kept current as the software changes.
- 04
The software shows its working.
When software built on our platform acts on your data, the action carries a reference. Open it and you see what it read, when, and under whose permissions, and you can re-run it yourself. Plausible but wrong is the fear that stops companies trusting AI with a decision. The answer is a click, not a promise.
What you holdThe action with its working: what it read, when, and under whose permissions.
At delivery you hold all of it: working software, its spec, its test record and the code. Software vendors own that code outright.
The kit of parts.
Every build adds to a kit we reuse: the identity and audit layer, the data platform, the knowledge platform and the interview platform. Each is built the same way, with the same record. We are opening the core pieces as open source, so what your software runs on is never a black box.
Talk to us.
We’ll walk you through a spec, a build record and an answer with its working attached, on one of our own platform builds.