ABOUT
The Seven Layer Model for Digital Public Infrastructure is a legal architecture for keeping Digital Public Functions legally valid, attributable, and contestable as Digital Public Services scale on Digital Public Infrastructure. It exists to prevent governance drift where delivery artefacts begin to substitute for lawful authority, institutional mandate, and authorised procedure, weakening evidence quality and making procedural remedy discretionary or vendor-dependent.
The Seven Layer Model in one page
The model organises the conditions that must remain operable for legal effect to be attributable and reviewable. It makes explicit the accountability chain from lawful authority through canonical records, service logic, execution outcomes, and oversight and remedy, so inspection readiness can be demonstrated at first reliance and re-tested at material change.
Why it exists?
The Seven Layer Model for Digital Public Infrastructure exists because many programmes fail through governance drift rather than lack of technology. When workflow defaults, procurement packaging, or vendor controls start behaving as implied authority, legal effect becomes difficult to attribute and procedural remedy becomes fragile. The model keeps lawful authority, institutional mandate, authorised procedure, and oversight and remedy operable so Digital Public Functions remain contestable as reliance expands.
Author and practice
Ott Sarv is the author of the Seven Layer Model for Digital Public Infrastructure and works as a legal and technical architect for end-to-end delivery. The work spans lawful authority and institutional mandate through authorised procedure, execution environments, and oversight and remedy, with a focus on inspection readiness and legal traceability. Code is not delivered, instead the output is operable legal architecture and technical architecture that implementation teams can execute and oversight bodies can inspect.
Working together
Work typically begins with a short diagnosis of the current legal architecture and technical architecture against the conditions required for lawful reliance and contestability. The engagement then defines sequencing gates and operability tests so authorised procedure, evidence pathways, and procedural remedy are inspection-ready before reliance expands further. Where confidentiality constraints apply, deliverables are structured to preserve them while still producing usable artefacts for institutions, implementers, and oversight bodies.
Typical outputs?
Typical outputs include legal inventory and competence mapping, mandate instruments with enforceable scope limits and change control, and accountability chains that link lawful authority to binding acts. Evidence pathways and evidence bundles are specified so independent reconstruction is possible, including evidentiary duties, retention expectations, correlation requirements, and audit access conditions. Governance specifications are produced for data exchange, controlled disclosure, consent operability, credential lifecycle controls, and decision logic governance so correction propagation, suspension, and reversal remain executable.
