top of page

Digital public infrastructure fails when guidance cannot be enforced

  • Writer: Ott Sarv
    Ott Sarv
  • Nov 1, 2025
  • 4 min read

Digital public infrastructure is being adopted at scale, yet many programmes still lack the compellable powers needed to suspend effect, correct records, and reverse outcomes when decisions are contested.


A contested record is the first real Digital public infrastructure test

Milestones can be met and services can remain stable, yet the first disputed case still breaks legitimacy if nobody can be compelled to pause binding outcomes while facts are repaired.


Digital Public Infrastructure (DPI), is a nationally governed, cross-domain foundation of shared capabilities and trust mechanisms that lets multiple public services operate at scale through common functions, interoperability arrangements, and assurance practices. DPI is not a single platform, not a donor toolkit, and not a reusable artefact that becomes lawful by default, legal effect arises only when a competent authority mandates a bounded public function inside a procedure authorised by law, with an accountable institution owning evidence and remedy.


Institutional mandate decides who can be compelled

Portable guidance can describe an end state, yet it does not assign enforceable decision rights that survive organisational change and supplier turnover, so operational forums begin substituting for lawful authority. Once that substitution occurs, coordination replaces compulsion, and responsibility fragments even when the technology performs.

A widely used 2024 framing positions DPI as shared and interoperable foundations in an official publication. Domestic enforceability follows only when a mandate instrument allocates powers, boundaries, correction duties, and review reach in a way that can be exercised on demand.


Procurement lock-in hardens dependency before governance

Contracts and integrations create irreversible reliance faster than institutions create enforceable control, so dependency paths harden before anyone proves that suspension, correction propagation, and reversal work across the reliance chain. Each new relying service increases the cost of change, which turns later governance into negotiation under pressure.


A 2025 approach document promotes DPI reuse as a public benefit in an official publication. Reuse becomes a risk multiplier when remedial powers are not operational across the full dependency surface.


Oversight and remedy separate legitimacy from service quality

Complaint intake does not constitute redress when it cannot change outcomes, stop downstream effect, and correct the authoritative record in a way that reaches dependent systems. Trust depends on whether oversight can compel evidence quickly and require corrective action that alters reality, not only whether a helpdesk responds.


A global compendium frames safeguards and inclusion as core concerns in an official publication. That framing remains incomplete in practice until a jurisdiction can demonstrate that remedy reaches live services, including reversal and correction propagation.


Authorised procedure prevents workflow defaults from becoming authority

Legal validity depends on procedure, not interface, because procedure defines who may act, how reasons are recorded, and how a person contests a decision. Workflow defaults often replace procedure during implementation, particularly when releases alter eligibility logic or decision sequencing, and the gap becomes visible only after reliance expands.


Evidence-grade reason giving and change authorisation are not compliance ornaments, they are the operating conditions for contestability at scale. If a programme cannot show who authorised a rule change and why, review becomes interpretive and remedy becomes inconsistent.


Digital public function is the unit of enforceable control

Public authority does not exist at platform scale, it exists at the level of a bounded function that can be mandated, executed, evidenced, and reversed. Control improves when leaders can name the function, assign an accountable institution, define the evidence pathway, and prove remedy reach under realistic conditions.


One governance sequencing approach that forces those decisions early is described in official document. The value is not the label, the value is the discipline of preventing downstream artefacts from substituting for upstream authority.


Initiation

Initiation is the last phase where institutions can keep options open while still protecting legitimacy, because dependency hardening has not yet become irreversible.

initiation control

decision that must be attributable

operational proof that must exist

duty holder assignment

one institution holds enforceable powers and boundaries for the relevant function

escalation compels action rather than requesting coordination

remedy reach definition

suspension and reversal authority extends across dependent services

halt and correction propagate across relying services

evidence obligations

evidence is defined as an inspection-ready capability

reconstruction works without ad hoc compilation

Intervention

Intervention succeeds when rule changes are treated as changes to public authority, rather than deployment events that sit outside institutional control.

intervention control

decision that must be attributable

operational proof that must exist

change authorisation

competent authority approves rule-impacting changes

versioning supports rollback and review at service speed

dependency governance

reliance surfaces are known and governed

corrections reach every dependent service consistently

incident authority

stop-effect power triggers quickly under defined conditions

remedy changes live outcomes rather than ticket status

Outcome

Outcome quality is demonstrated by correction performance, not by availability metrics alone, because a stable system can still produce invalid legal effects.

Suspension must work across dependencies, corrections must propagate, and reversals must restore rights without improvisation, otherwise the programme scales dispute.


The incentive trap that keeps repeating

Donor incentives reward early rollout, delivery incentives reward visible progress, and institutional incentives postpone hard mandate decisions until disputes force them. Which institution will be compelled to stop effect and reverse a binding outcome when reliance expands faster than governance?


Confidence follows from correction that works, because operational remedy is the public’s proof that authority remains accountable.

The governance decision that cannot be deferred

The opening tension returns as soon as the first contested outcome arrives, stable systems still fail legitimacy when no duty holder can be compelled to suspend effect and correct downstream outcomes. Digital public infrastructure becomes decision-safe only when compellability is treated as a precondition for scale, so the institutional choice is clear, will reliance expansion be gated on enforceable remedy, or will the first dispute define governance in public?


What should happen next

Block national scale until a named duty holder can suspend effect, propagate corrections, and reverse outcomes across dependencies under oversight.

Comments


bottom of page