◆
Defensible later
The record of what was done and why survives the people who did it. An inquiry years from now gets a straight answer.
Public services carry an unusual burden: they must work for everyone, be explicable to anyone, and be defensible years later to people who were not there. Most infrastructure is built for none of those.
Used for citizen-facing services, case management, records and inter-agency reporting.
What this looks like in practice
The record of what was done and why survives the people who did it. An inquiry years from now gets a straight answer.
A figure you can take into a budget cycle and be held to, rather than a variable you explain afterwards.
What you build remains yours and remains portable. Leaving is a decision, not an escape.
Services here run for decades. The arrangement assumes the original team will not be the one maintaining it.
Public bodies are often slow not from caution but from the cost of justification. Make justification cheap and the caution stops being expensive.
Someone asks, four years on, what this service did in a particular month and why it was changed. The people involved have moved on. The answer is still there, complete, and nobody has to reconstruct it from memory and email. That is the difference between a record and a recollection.
Citizen-facing surfaces that hold up on old devices, slow connections and assistive technology.
Internal tooling that can improve on a normal cadence, because the people using it deserve that.
Portability, cost certainty and an exit that is a decision rather than an emergency.
Data moving between bodies with the separation and record-keeping that demands.
The question that used to take a month of archaeology now takes an afternoon, and the answer is better.
What you build stays yours and can be exported. We would rather you stay because leaving is easy than because it is hard, and procurement rules tend to agree.
Yes. You will have a figure before the cycle starts, and growth will move it in a direction and magnitude you anticipated rather than discovering mid-year.
That is assumed rather than hoped against. The arrangement is legible to whoever arrives, and the record of why things are as they are does not depend on anyone remembering.
Yes, and most do. One service, nothing decommissioned, and a decision about the rest taken once you have seen it carry real public load.
Run regulated workloads with a complete record of every change, and answer an auditor in an afternoon rather than a quarter.
Carry sensitive workloads with separation that is structural, and keep clinical and research software moving.
Hold up on the day that matters most, and change your storefront in the week you decided to, not the quarter after.
Publish the moment it matters, carry an audience that arrives all at once, and keep an archive that stays reachable.
Bring plant data somewhere useful, keep the software near the line dependable, and stop treating the factory as offline.
Carry metering and grid data at full fidelity, and run customer systems that hold up when everyone calls at once.
Begin with one workload. Keep what you have running. Decide whether to continue once you have seen it carry something real.
No migration required to begin. Nothing to tear down if you stop.