Software can be built and delivered faster than anyone can review it. AI assistants removed the constraint that used to bound how much software an organization created: the number of people who could write code.
For enterprises now facing a sprawl of independently built applications, there is finally a way to govern it without dictating how any of it gets built, and a reliable way to say how far any release can be trusted: how much of it may deploy, integrate, or act with nobody watching.
The Governed Delivery Platform is the reference implementation. It is a build pipeline much like the one your teams already run, with one thing added. For every release it answers a question those tools do not ask: how much of this may be handed over without a person? It answers from what the pipeline measured, not from what anyone claimed, and it names the specific missing evidence holding each release back, so the next step is always concrete.
Walk through it yourself
- WHAT HAPPENS WHEN YOU OPEN IT
- A guided tour starts on its own and takes about ten minutes. Nothing to install, no sign-up, nothing you can break. The site is published read-only.
- WHAT IT SHOWS YOU
- One application's real delivery history, run by run: the evidence each build produced, how much authority that earned it, and the point at which a release is refused. Every log, coverage figure and decision in it came out of an actual pipeline run.
- THE PART WORTH SLOWING DOWN FOR
- Two builds share an identical score of 76 out of 100. One is released, the other refused. The score describes what is known about the work. It does not make the decision.
Or see it built in front of you
- WHAT HAPPENS
- About twenty minutes, walked through with you, or with your own login by arrangement. An application somebody built in an afternoon, with no tests, no review, just prompt engineering, is brought under governance while you watch.
- WHAT IT SHOWS YOU
- How a pipeline is generated, how its first build runs, and how the resulting measurement is explained. Then the same platform against an application built the governed way, which clears its first release inside two runs.
- THE PART WORTH SLOWING DOWN FOR
- The first application scores 29 out of 100, and is permitted nothing: not deployment, not integration, not being relied upon by a person. None of it was arranged beforehand.
What it comes down to
A score tells you how much is known about a system. An authority level decides what may happen without a person. Organizations that treat those as the same thing either release work they cannot defend or block work they could have shipped, and afterwards cannot tell which they did.
The framework allows autonomy in how software gets built, without standardising on any one pipeline. It is published openly for anyone to implement, including the platforms your teams already use.
Govern the pipeline.Control the authority.
Where to go next
- wekid.orgStart here: what the framework is, and the problem it exists to solve.
- wekid.org/framework.htmlThe framework itself: the five layers of what a system knows, and the five levels of authority that knowledge can earn.
- wekid.org/resources.htmlThe research behind it: papers, templates and reference material.
- wekid.org/enterprise.htmlFor enterprises: how to build and deploy in your own organisation what these demonstrations show.
- wekid.org/partners.htmlFor platform and tooling vendors: how to implement the framework inside your own product.
- wekid.org/certs.htmlTraining and certification, to get your own teams applying it.