
An AI adoption engagement run at two altitudes: the whole estate of tools seen from above, and one team putting a single one of them to work.
A tool for seeing every AI tool a company is using, and for getting one of them properly adopted.
AI tools arrive from everywhere: bought centrally, expensed by a team, or opened in a browser tab by one person. Nobody holds the list, so nobody can say what is approved, what is risky, or what any of it is returning.
Governor works at two heights. From above it shows the whole estate of tools and the state of each one. From ground level it follows a single team through the five stages of putting one tool to work.
Airport Authority Hong Kong is inviting organisations with proven capability to tender for dedicated corporate AI infrastructure and operating services. The public notice does not disclose the architecture or the intended use cases, and this page does not infer them.
The phrase operating services is the useful signal. Production AI needs an ongoing answer to who can use it, what it may touch, which decisions remain with people and what happens when its output is wrong. Governor makes those questions visible before a pilot crosses into everyday work.
Current signal: Airport Authority Hong Kong tender notice, closing 4:30 p.m. HKT on 15 September 2026. Governor is an Enzwa concept, not work for the Airport Authority or a tender response.
Maturity models, autonomy ladders, augmentation spectrums and governance frameworks are nearly always presented side by side, as though the job is to pick the one that suits the organisation.
In a real engagement they sequence. You assess where you are, frame what AI should do and who decides, design the loop, govern the scale-up, then embed it with the team. Each decision compounds into the next, which is why choosing a framework is not the same as having a programme.
Not the ambition, the position. Where the organisation actually sits, function by function, before anything is promised to a board.
How far a tool may act on its own, and which decisions stay with a person. Set per use case rather than once for the whole organisation.
Where the tool sits in the work: what it drafts, what it checks, what it hands back, and what a person still owns end to end.
Feedback has to be a discipline rather than a goodwill exercise, because error and drift compound over iterations and nobody notices until the output is wrong in a meeting.
The stage most programmes never reach. Governance that survives more than three use cases, and a teaming model the floor can actually work inside.
Governor scores a portfolio across eight use-case domains, then asks the only question that changes the shape of the engagement. Every other decision is downstream of this one.
The top three use cases only. Enough surface to prove the model works and to find out what governance actually has to cover.
Five at once. Enough running in parallel that the organisation starts to expect it, and enough load to test whether the loop holds.
All eight domains together. The fastest route to scale and the widest exposure, taken before the governance from stage five is anywhere near ready.
A pilot proves a tool can do the work. Production asks a different set of questions: who owns the output, what happens when it is wrong, which system of record it writes to, and who is accountable in an audit.
Those questions belong to stage five, and most programmes are still congratulating themselves on stage one when they meet them. Governor models the chasm explicitly, so the cost of crossing it is in the plan before the pilot is signed off rather than discovered afterwards.
The second view follows one team through the same five stages with one tool. This is where a governance model either survives contact with the work or turns out to have been a slide.
Proficiency does not arrive with the licence. It ramps, unevenly, and it dips first: the early weeks cost time rather than save it, because people are learning where the tool is reliable and where it is confidently wrong. A programme that reports on month one kills itself.
Illustrative proficiency ramp for one team on one use case. The shape is the finding; the values are Governor’s synthetic portfolio.
The first GenA.I. Sandbox++ cohort selected 36 use cases from nearly 100 proposals. It involves 30 financial institutions and 27 technology partners. The regulators say the cohort will test end-to-end processes and dynamic oversight of actions taken by other AI applications.
That is the two-altitude problem Governor is designed to explain: control across a portfolio, then decision rights inside one working process.
Source: HKMA, SFC, IA and MPFA announcement, 27 August 2026. Counts are official. Governor's five stages, eight domains and proficiency ramp are an illustrative Enzwa model.
Govern the estate from above, then drop down and follow a single team through maturity, autonomy, augmentation, the learning loop and teaming. The business case assembles itself as you go, because each stage is built from the answer to the one before it.
Open Governor →