Architectural domain · Arts. 94–96 · proposed internal function
Technical authority
Final technical authority means deciding architecture and technical acceptability within its proper domain — not deciding a legal outcome that belongs to judges, the National Assembly, the Government, the electoral authority, the Central Bank or the Civil Registry.
Pre-Foundation · constitutional office not activatedConstitutional Proposal · reference text · not promulgated
What falls within the architectural domain
Computing infrastructure, communication, processing, storage, deployment, observability, performance, security, redundancy, recovery, interfaces and spatial representation. Within this space, the Architect may define architecture, standards, target state, deployment sequence, security requirements and technical-acceptability criteria.
Technical authority is not an absolute credential
It is
- Defining architecture and technical requirements.
- Directing technical teams within legal parameters.
- Rejecting a solution on objective and reasoned technical-risk grounds.
- Defining recovery, portability and technical acceptability.
It is not
- Exclusive possession of a root credential.
- Exemption from segregation of duties.
- Power to approve a legal act reserved to another institution.
- Economic power to choose one’s own related counterparty.
Procurement and conflicts of interest
Where a technical requirement materially reduces competition and may benefit a related provider, external technical review, an economic decision by a disinterested authority, comparative benchmarking and Court of Audit controls apply. Technical competence is preserved; the economic interest is isolated.