Principles
The principles Public Framework is built on
Twenty commitments that guide the metamodel, the application and the way institutions describe how they work.
Digitalization must have purpose, not just technology.
The goal is not to deploy applications but to genuinely solve the problems of citizens and civil servants.
Modeling comes before implementation.
No system is designed without a clear understanding of the processes it serves.
The process defines the application, not the other way around.
IT solutions must reflect real processes, not force them to conform to technology.
Institutions must become able to define their own requirements.
The civil servant is not only a beneficiary but the operational architect of digital transformation.
All actors must speak the same language.
A shared vocabulary is needed between administration, suppliers, citizens and consultants.
The framework is alive and adaptable.
Public Framework evolves together with society, technology and legislation.
Reuse is more valuable than reinvention.
Models, documents and architectural components must be reusable and shareable.
Documentation is a right, not a chore.
Every system must come with clear, accessible and up-to-date documentation.
Interoperability is not a bonus, it is a requirement.
All digital solutions must be designed to communicate with each other.
Versions must be managed as in product engineering.
Architecture, requirements and processes must be versioned and traceable.
Security is fundamental, not optional.
Every digital component must meet clear security and confidentiality standards.
Quality is everyone’s responsibility.
From civil servant to architect, from analyst to tester, everyone contributes to the result.
The citizen is a beneficiary, not merely a user.
Interfaces, processes and decisions must be centered on the citizen’s real experience and needs.
Governance must be clear, distributed and functional.
Roles and responsibilities must be defined at technical, legal and operational level.
Every error must have a code and a lesson.
Systemic errors must be catalogued, analyzed and used to learn and prevent.
Simplicity is an architectural quality.
A good system is one that can be understood by those who use and administer it.
Data must flow, not get stuck.
Access to data must be regulated, not blocked — it must support decisions and public service.
Transparency is a form of quality control.
When processes are transparent, quality and trust grow naturally.
Standards are pillars of cooperation.
Public Framework aligns with international standards and adapts them where needed.
Without trust, digitalization is only a technical effort.
Trust is built through clarity, collaboration and tangible results.