technical governance
Technical governance of infrastructure
Architecture, deployment, observability, performance, security, redundancy and spatial representation belong to the technical domain; legal effects remain with the competent normative or institutional authority.
Architecture ≠ sovereigntyTechnical execution ≠ legal authorisationSegregation of duties
A technical decision can be important without becoming law
Choosing a graphics engine, database, topology, cache, coordinate system, protocol or infrastructure belongs to the architectural domain. If a mechanism begins to directly produce a tax, sanction, title, vote or another reserved effect, the normative parameters of the competent authority prevail.
Four functions that should not collapse into one person
Architectural decision
Defines a technical solution within constitutional limits.
Legal authorisation
Confirms competence and the act when the effect requires institutional authority.
Privileged execution
Technically carries out the approved change.
Audit/recovery
Enables reconstruction and accountability without creating a new technical sovereign.
Related pages
How this page connects to Sistema Candeia
CompetenceTechnical architecture may define how to execute; it cannot create legal competence or an outcome reserved to another body.
Candeia OSThe current structure brings institutional areas together in one environment without merging their competences.
ControlMaterial changes must preserve auditability, privilege segregation, portability and appropriate institutional review.