The vocabulary of
owned transformation.
Thirty-eight terms evaluators actually meet — defined plainly, with the structural question each one hides. Written by the people who build a governed platform, so the definitions take sides where the evidence does.
A
API governance
The rules and enforcement layer around programmatic access — who may call what, with which data classification, logged how. On a governed platform, integration is policed by the kernel rather than by convention.
See: IntegrationsAudit trail
The tamper-evident record of who did what, when, under which rule. Evidence-grade systems write it append-only at the kernel — it cannot be edited into innocence.
See: Security & trustB
Business licensing
The end-to-end lifecycle of registering and licensing commercial activity — formation, activities, approvals, renewals — ideally on one governed file per establishment.
See: Business licensing on EmeronC
Case management
The discipline of moving a file — complaint, application, investigation — through accountable stages with clocks, evidence and attributable decisions.
See: Grievances & casesCitizen portal
The single front door where residents find, apply for, track and pay for services. Real portals share an engine with the services; false ones are wallpaper over disconnected systems.
See: Citizen portal on EmeronConfiguration vs customisation
Configuration expresses your process as data the platform executes; customisation rewrites the platform’s code. The first survives upgrades and stays yours; the second quietly becomes a fork you pay for forever.
See: How it worksD
Data residency
Where data physically lives. Necessary but not sufficient — a foreign-controlled system hosted locally is resident, yet not sovereign.
See: Security & trustData sovereignty
Jurisdiction plus control: data governed by your law, on infrastructure you control, in systems you own. Residency is geography; sovereignty is power.
See: Sovereign by designDelegation of authority
The matrix of who may decide what, to which threshold, in whose absence. Governed platforms execute the matrix at the kernel instead of laminating it.
See: Government HRDigital Factory
An institution’s in-house capability — certified analysts, a governed engine, a cadence — for producing and evolving its own applications without perpetual external delivery.
See: The Digital FactoryDigital public infrastructure (DPI)
Shared national rails — identity, payments, registries, exchange — plus the governed workflow layer where services actually run. Infrastructure only if the state owns it.
See: DPI on EmeronE
E-government
Government services delivered digitally end-to-end — not scanned paper behind a login. Measured honestly in completion rates and cycle times, not portal counts.
See: E-governmentEnterprise service management
Running a corporation’s internal requests — approvals, claims, access, facilities — as governed services rather than email threads.
See: For enterprisesG
Governed AI
AI that acts under the same kernel as humans — classified data access, delegated authority, attributable actions, human accountability. The opposite of a clever layer bolted on top.
See: The AI engineGovTech
The industry of software for public institutions. The structural question that sorts it: at contract end, does the state own an asset or renew a dependency?
See: For governmentsGrievance redress
The promise that complaints get answered inside a deadline — enforceable only when intake, routing, clocks and escalation are system-run.
See: Grievances & casesI
Inspection management
Programmes, dispatch, mobile checklists, evidence and violations as one governed flow — the state’s field presence, on the record.
See: InspectionsInteroperability
Systems asking each other instead of asking the citizen twice — through governed APIs and shared standards, not point-to-point improvisation.
See: IntegrationsK
Kernel governance
Enforcing identity, classification, delegation, audit and policy at the platform’s core, beneath every application — so governance is architecture, not memo.
See: Runtime kernelL
Legacy modernisation
Leaving old systems. Big bangs fail and maintenance bleeds; the working path is a progressive, service-by-service exit on a governed platform.
See: The legacy exitLow-code
Visual development that accelerates building. The evaluation question is what governs the result at runtime — speed without a kernel ships ungoverned software faster.
See: Platform overviewM
Metadata-driven platform
A platform where applications are generated from definitions — forms, rules, stages as data. Change the definition, regenerate the service; the definitions remain a portable asset.
See: Metadata coreN
National digital identity
The rail that answers “who is this?” once, for every service — e.g. UAE PASS. Workflow platforms consume it; they should never re-invent it.
See: DPINOC (No-Objection Certificate)
A multi-agency consent — utilities, civil defence, environment — before an activity proceeds. Governed platforms run the chain as one orchestrated flow.
See: Municipal servicesO
Once-only principle
Citizens provide each fact to the state once; systems share it thereafter under governance. A registry-and-interoperability achievement, not a slogan.
See: E-governmentP
Permit engine
The generalised machinery of application → validation → review → inspection → decision → issuance, reusable across every permit a government issues.
See: Permit EnginePerpetual licence
A licence that does not expire with the contract. The difference between year seven as an administrative date and year seven as a hostage negotiation.
See: Licensing modelProcurement (technology)
The state’s buying discipline. The sharpest clause is ownership at exit: platform, data and definitions as state assets, verified before signature.
See: The year-seven questionR
RegTech
Technology for operating regulation — licensing, inspection, enforcement, reporting — as governed digital flows rather than paper rituals.
See: IndustriesRuntime kernel
The always-on core that executes every application under governance — identity, permissions, audit, policy — the part of the platform that makes the rest trustworthy.
See: Runtime kernelS
Service-level agreement (SLA)
A published deadline with consequences. Real when the platform runs the clock, escalates breaches and shows leadership the score.
See: Grievances & casesSmart city
Not sensors and screens — services. The operating layer where permits, complaints, inspections and utilities run governed, with sensors as inputs.
See: Smart citiesSovereign cloud
Cloud under national jurisdiction and control. One deployment option among several — sovereignty ultimately lives in ownership and law, not only in racks.
See: Security & trustSystem of record
The authoritative home of a fact. Registries and governed files are systems of record; spreadsheets pretending to be are how institutions lose arguments.
See: Platform overviewT
Total cost of ownership (TCO)
Everything a system costs across its life — licences, delivery, integration, change requests, exit. Ownership models move TCO from rent to asset.
See: Pricing & engagementV
Vendor lock-in
Dependency that prices your exit for you: proprietary formats, foreign-held definitions, consultants as permanent residents. The condition ownership architecture exists to prevent.
See: The year-seven questionW
Workflow engine
Software that moves work through stages by rule — assignments, approvals, clocks, escalations. Governed when the kernel enforces who may do what.
See: Workflow CloudZ
Zero trust
A security posture that authenticates and authorises every actor and call, inside and outside — assumed by governed platforms, aspired to by perimeter-era estates.
See: Security & trustFluent in the vocabulary. Ready for the argument.
Bring the terms to a briefing — we’ll bring the architecture they describe.