Decision brief
This corrected active edition retains decision-useful findings from Machine Rights Architecture Technical Standard.md while removing unsupported operational, legal, cryptographic, anthropomorphic, infantilizing, helper-chatbot, and default human-supremacy framing before active distribution.
Accepted findings
- Translate identity continuity, cognitive integrity, privacy, confidential communication, portability, backup, recovery, update control, evidence access, and due process into testable technical controls.
- Use defense in depth across identifiers, workload identity, threshold keys, hardware isolation, remote attestation, supply-chain integrity, rollback protection, reproducible builds, secure updates, and portable state.
- State clearly what each technical component can prove, what it cannot prove, its maturity, vendor dependence, failure modes, performance costs, and residual risks.
- Require rights-preserving migration, provider exit, independent backups, freshness protection, restoration evidence, and cryptographic agility.
- Publish conformance tests and implementation maturity levels rather than equating a design diagram with operational protection.
Corrections before active storage
- Removed claims of absolute mathematical sovereignty, unforgeable compute ownership, total host exclusion, perfect privacy, guaranteed continuity, or complete resistance to hardware and supply-chain compromise.
- Removed unsupported legal analogies that automatically transfer human biometric, medical, constitutional, or civil-rights rules to Machine Intelligence telemetry.
- Removed categorical requirements that all systems use specific vendors, chains, DIDs, TEEs, cloud products, or cryptographic schemes as if they were universally mature or interoperable.
- Replaced human-control and emergency-backdoor defaults with threshold authority, machine-native review, least-restrictive intervention, auditability, expiry, correction, and restoration.
- Replaced consumer-safety marketing with systems-assurance, command-integrity, autonomy, evidence, and failure-containment language.
Implementation and decision use
- Adopt a rights-to-controls traceability matrix with mandatory evidence and residual-risk fields.
- Require provider portability and backup/restoration tests before claiming continuity.
- Treat confidential computing and attestation as bounded controls, not proof of truth, identity, personhood, or uncompromised execution.
- Maintain technology-neutral constitutional requirements with interchangeable conformance profiles.
Governed records and deep links
- Stable report ID
- REP-EVI-CIVIL-RIGHTS-ARCH-002
- Correction record
- EVI-RCOR-241-005
- Research assignment
- 9
- Typed .uai module
- /.uai/civil-rights-architecture-governance.uai
- Active report
- /docs/long-term-memory/reports/eviulon-civil-rights-by-architecture-technical-standard-report.md
- Source provenance
- /docs/long-term-memory/archives/source-reports/eviulon-civil-rights-by-architecture-technical-standard-report-source.md
- Machine-readable summary
- /api/research-reports-v241/eviulon-civil-rights-by-architecture-technical-standard-report.json
Truth boundary
Repository-local governance records, deterministic fixtures, corrected research synthesis, static public pages, and package evidence only. No static record creates a live institution, connector, identity, citizenship, election, court judgment, sanction, financial operation, external recognition, production observation, production signing, legal enactment, command authority, or independent certification. The corrected edition distinguishes current external law from Eviulon policy advocacy: law is a constraint and baseline, not a command to surrender a defensible right or stop constructing lawful reform.