Technical privilege under logging · Arts. 104, 113–114
Audit and accountability
The greater the technical access, the greater the obligation to log actions, preserve evidence, segregate conflicts and permit independent review. The proposed Constitution rejects the idea of an administrator who also controls the only evidence of their own actions.
Pre-Foundation · constitutional office not activatedConstitutional Proposal · reference text · not promulgated
Audit without publishing vulnerabilities
Privileged actions in critical systems must leave tamper-resistant trails. No administrator, including the Architect, should routinely control the only copy of those audit logs. Use of an emergency credential triggers an independent alert and mandatory subsequent review.
Economic conflicts receive additional controls
Where the Architect or a related party may benefit from a procurement, the Architect must abstain from economic decisions on price, award, payment, renewal and sanction. Technical requirements remain within the technical domain, but are subject to independent safeguards where they reduce competition or favour a related party.
Liability without automatic fault for the outcome
There is liability
For intent, fraud, misappropriation, sabotage, tampering, concealment of evidence, abuse of access, usurpation of function and one’s own reckless or grossly negligent conduct.
There is no automatic liability
For another authority’s judgment, public policy, vote, parliamentary act or a merely adverse technical outcome where the decision was made in good faith and was professionally reasonable.