105
canonical record types in one operating system
Seven applications on one database, and one definition of each business fact across all of them. Not 105 tables in 18 tools that disagree — 105 record types with one authoritative home each.
02 / OUTCOMES
Outcomes
7 records
An outcome exists on this page only if the number is real, the source is a published case study, and the attribution is defensible. There is no estimated or projected state. A number that stops being true fails the build.
870+
automated tests, green, framework-free
The tests are written against the rules the business depends on: routing, permissions, agent boundaries, degradation and data behaviour. A build fails if a retired proof number appears anywhere in the repository.
3,828
boundary crossings attempted in the test suite, all refused
Every agent is tried against every permanently human-owned decision at every autonomy rung, and every attempt is confirmed to fail. A rule nobody can cross is worth more than a policy everybody has read.
33
governed AI agents, every one deployed at OBSERVE
Each carries an identity card: what it reads, what it writes, whether it may contact a customer, where it reports, and its ceiling. No card, no deploy. Connecting a language model changes no agent's autonomy.
29
decisions owned by a human, permanently
Credit submissions, deal terms, vehicle claims, disputes and legal commitments are not on a roadmap toward automation. They are fixed to a person, and the test suite proves no agent can reach them.
76
commits in four days, every step reported and gated
Speed came after the operating rules were written down, not instead of them. Each phase reported what it had done and what it had not before the next one opened.
7
applications running on one database
Five operating applications and two tenancy applications, plus four websites. One login sees the whole company, because there is one company to see rather than seven subscriptions pointed at each other.
NOT YET MEASURED
Say we do not know yet.
5 records
The numbers above are properties of software ARK built. The numbers a buyer wants — the economic ones — are below, without figures, because no customer transaction has run on the system. Each one says what is blocking it. When a figure is measured it moves up, with its source.
Cost per funded deal
STATUS
Unmeasured
WHY
Ad spend is not yet a record in the platform, so the chain from creative to funded transaction cannot close without a manual step.
UNBLOCKED BY
Connecting the ad platforms to the attribution layer.
Gross profit per lead
STATUS
Unmeasured
WHY
No customer transaction has run on the system. Every figure would be a design target wearing a result's clothes.
UNBLOCKED BY
The first hundred Winnipeg garages, live.
Administrative hours removed
STATUS
Unmeasured
WHY
The before-state was never timed at the client. A saving measured against a guess is a guess.
UNBLOCKED BY
A timed baseline taken during the audit, before anything is built.
Verified economic value created
STATUS
Unmeasured
WHY
Attribution has to be defensible before it is publishable. Claiming every improvement was caused entirely by ARK would not survive scrutiny.
UNBLOCKED BY
Twelve months of operation against a measured baseline.
Lead to sale rate, per lane
STATUS
Unmeasured
WHY
The platform records the ladder as events and reports four lanes side by side. With no live traffic, every lane reads not measured.
UNBLOCKED BY
Real traffic through the consent line.
The first of these is unblocked by the attribution layer. The rest are unblocked by launch.