Kerala Rising: From Exporting People to Exporting Ideas · Page 284 of 353

KERALA RISING · FROM EXPORTING PEOPLE TO EXPORTING IDEAS

KERALA RISING · FROM EXPORTING PEOPLE TO EXPORTING IDEAS
‘The state cannot build software. This will fail like other
government IT.’
Government IT fails most reliably when it is
procured as a one-off deliverable from a vendor with
no stake in its longevity, staffed by a rotating cast of
contractors, owned by no one, and audited by
nobody until it is too late. The institution is designed
as the opposite of each of those: a permanent body
with retained Kerala-based engineers, public
ownership, continuous quarterly audit, CAG
jurisdiction, and a published unwind protocol. The
precedents that worked, UPI, Aadhaar, Estonia’s XRoad, Singapore’s GovTech; all share that
institutional shape, and all were built by states. The
objection is really an argument against the
procurement model, and the institution is the
answer to it, not an example of it.
‘What if the next government kills it?’
The structures in Chapter 15 are chosen specifically
to make this hard and pointless, so the answer here
can be brief. Those safeguards, taken together,
mean the institution is not a partisan project a
successor inherits as a liability; it is permanent civic
infrastructure that produces visible, audited
outcomes a successor would have to explain
destroying. No structure is immortal. But this one is
built to be boring to attack, expensive to dismantle,
and embarrassing to cancel while it is visibly
284