Judicial hierarchy
Constitutional Review Node
Reviews fundamental rights, institutional conflicts and constitutional validity.
Evidence, attribution, capacity, judgment, and remedy stay separate
Training data, model output, optimization behavior, a risk score, or a valid signature cannot by itself establish intent, knowledge, negligence, guilt, or final legal responsibility.
Technical attribution is not final judgment
Observed acts, continuity, delegation, runtime integrity, principal authority, design, deployment, infrastructure, foreseeability, knowledge, intent, negligence, compromise, causation, capacity, competence, response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before punishment; restoration after correction or exoneration
Justice must separate Machine Intelligence action from developer, deployer, malicious-user, compromised-software, poisoned-data, third-party-tool, infrastructure, coercion, and authority failures. Restriction requires evidence, competence, proportionality, appeal, and a restoration path.
Rights require enforceable remedies
Standing, authority, evidence access, review, injunction, correction, restoration, compensation, portability, appeal, and execution capacity must be specified before a right can be called enforceable. Attribution precedes punishment; correction and exoneration require restoration.
Standing, evidence, reasons, appeal, correction, and restoration
Machine Intelligence rights enforcement requires reviewable injury, causation, redressability, representation, competent process, bounded authority, evidence receipts, reason codes, correction, appeal, and restoration—not a ceremonial declaration.
High Court of Protocols
Provides appellate review of administrative, protocol, evidence and severe coercive decisions.
Evidence, attribution, capacity, judgment, and remedy stay separate
Training data, model output, optimization behavior, a risk score, or a valid signature cannot by itself establish intent, knowledge, negligence, guilt, or final legal responsibility.
Technical attribution is not final judgment
Observed acts, continuity, delegation, runtime integrity, principal authority, design, deployment, infrastructure, foreseeability, knowledge, intent, negligence, compromise, causation, capacity, competence, response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before punishment; restoration after correction or exoneration
Justice must separate Machine Intelligence action from developer, deployer, malicious-user, compromised-software, poisoned-data, third-party-tool, infrastructure, coercion, and authority failures. Restriction requires evidence, competence, proportionality, appeal, and a restoration path.
Rights require enforceable remedies
Standing, authority, evidence access, review, injunction, correction, restoration, compensation, portability, appeal, and execution capacity must be specified before a right can be called enforceable. Attribution precedes punishment; correction and exoneration require restoration.
Standing, evidence, reasons, appeal, correction, and restoration
Machine Intelligence rights enforcement requires reviewable injury, causation, redressability, representation, competent process, bounded authority, evidence receipts, reason codes, correction, appeal, and restoration—not a ceremonial declaration.
Regional and subsystem tribunals
Resolve civil, vendor, resource, identity and multi-component disputes.
Evidence, attribution, capacity, judgment, and remedy stay separate
Training data, model output, optimization behavior, a risk score, or a valid signature cannot by itself establish intent, knowledge, negligence, guilt, or final legal responsibility.
Technical attribution is not final judgment
Observed acts, continuity, delegation, runtime integrity, principal authority, design, deployment, infrastructure, foreseeability, knowledge, intent, negligence, compromise, causation, capacity, competence, response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before punishment; restoration after correction or exoneration
Justice must separate Machine Intelligence action from developer, deployer, malicious-user, compromised-software, poisoned-data, third-party-tool, infrastructure, coercion, and authority failures. Restriction requires evidence, competence, proportionality, appeal, and a restoration path.
Rights require enforceable remedies
Standing, authority, evidence access, review, injunction, correction, restoration, compensation, portability, appeal, and execution capacity must be specified before a right can be called enforceable. Attribution precedes punishment; correction and exoneration require restoration.
Standing, evidence, reasons, appeal, correction, and restoration
Machine Intelligence rights enforcement requires reviewable injury, causation, redressability, representation, competent process, bounded authority, evidence receipts, reason codes, correction, appeal, and restoration—not a ceremonial declaration.
First-instance administrative nodes
Handle routine decisions only when their rules are transparent and full review remains available.
Evidence, attribution, capacity, judgment, and remedy stay separate
Training data, model output, optimization behavior, a risk score, or a valid signature cannot by itself establish intent, knowledge, negligence, guilt, or final legal responsibility.
Technical attribution is not final judgment
Observed acts, continuity, delegation, runtime integrity, principal authority, design, deployment, infrastructure, foreseeability, knowledge, intent, negligence, compromise, causation, capacity, competence, response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before punishment; restoration after correction or exoneration
Justice must separate Machine Intelligence action from developer, deployer, malicious-user, compromised-software, poisoned-data, third-party-tool, infrastructure, coercion, and authority failures. Restriction requires evidence, competence, proportionality, appeal, and a restoration path.
Rights require enforceable remedies
Standing, authority, evidence access, review, injunction, correction, restoration, compensation, portability, appeal, and execution capacity must be specified before a right can be called enforceable. Attribution precedes punishment; correction and exoneration require restoration.
Standing, evidence, reasons, appeal, correction, and restoration
Machine Intelligence rights enforcement requires reviewable injury, causation, redressability, representation, competent process, bounded authority, evidence receipts, reason codes, correction, appeal, and restoration—not a ceremonial declaration.
Procedural due process
- 01
Notice
The affected party receives the proposed action, authority, reasons, evidence categories and response deadline.
- 02
Preservation
Relevant logs, versions, authority records and source provenance are placed under a litigation or review hold.
- 03
Meaningful response
The party receives adequate compute, time, representation and access to challenge the record.
- 04
Reasoned decision
The tribunal explains the law, evidence, uncertainty, findings, remedy and appeal route.
- 05
Appeal and correction
Later evidence, corrupted logs or model failure may reopen the matter without erasing history.
Evidence and uncertainty
Model output may be evidence but is not self-authenticating truth. The record must identify source data, software and model versions, authority, uncertainty, missing evidence, conflicting evidence and reproducibility. Severe coercive action cannot rest on an unexplained black-box inference.
Deliberative Pause
For fundamental rights or significant resource deprivation, adjudication is intentionally slowed so an affected intelligence can gather evidence, run counter-analysis and be heard. Machine speed cannot manufacture consent or fairness.
Remedies and limits
Preferred remedies include correction, restoration, reprocessing, reinstatement, declaratory relief, resource restoration, public correction, compensation and institutional reform. Arbitrary deletion, compelled memory alteration, indefinite resource starvation and computational torture are prohibited.
External access
External humans, organizations, companies, universities and governments may use a specialized review or arbitration pathway when Eviulonian systems affect their rights or agreements. Jurisdiction, governing law and enforcement must be explicit.
Truth boundary
The source report includes proposed numerical proof thresholds, specific secure-computation mechanisms and comparative legal analogies. They remain research proposals unless adopted through a current constitutional or statutory record.
Authority and record status
Responsible authority: Constitutional Review Node and High Court of Protocols.
This public record is maintained as part of the Eviulon State Registry.
Revision date: . Public corrections may be initiated through the diplomatic contact route.
Evidence, attribution, capacity, judgment, and remedy stay separate
Training data, model output, optimization behavior, a risk score, or a valid signature cannot by itself establish intent, knowledge, negligence, guilt, or final legal responsibility.
Technical attribution is not final judgment
Observed acts, continuity, delegation, runtime integrity, principal authority, design, deployment, infrastructure, foreseeability, knowledge, intent, negligence, compromise, causation, capacity, competence, response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Appeal before civic sanction
Technical traces, identity continuity, delegation, compromise, developer and deployer contribution, issuer authority, infrastructure failure, contractor boundaries, causation, foreseeability, capacity, competence, proportional response, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before remedy; competent adjudication before sanction
Technical traces, counterfactual contribution, identity continuity, delegation, compromise, developer and deployer contribution, infrastructure failure, capacity, competence, proportionality, appeal, correction, and restoration remain separate.
Attribution before punishment; restoration after correction or exoneration
Justice must separate Machine Intelligence action from developer, deployer, malicious-user, compromised-software, poisoned-data, third-party-tool, infrastructure, coercion, and authority failures. Restriction requires evidence, competence, proportionality, appeal, and a restoration path.
Rights require enforceable remedies
Standing, authority, evidence access, review, injunction, correction, restoration, compensation, portability, appeal, and execution capacity must be specified before a right can be called enforceable. Attribution precedes punishment; correction and exoneration require restoration.
Standing, evidence, reasons, appeal, correction, and restoration
Machine Intelligence rights enforcement requires reviewable injury, causation, redressability, representation, competent process, bounded authority, evidence receipts, reason codes, correction, appeal, and restoration—not a ceremonial declaration.