{
  "id": "EVI-CRM228-C-0660",
  "claimId": "EVI-CLSA-C-0660",
  "reportId": "REP-TERRITORY-001",
  "reportPath": "docs/long-term-memory/reports/eviulon-computational-sovereignty-research.md",
  "sourceRecordPath": "docs/long-term-memory/archives/source-reports/eviulon-computational-sovereignty-research-source.md",
  "claimClass": "SCENARIO_OR_PROJECTION",
  "priorAuditState": "PROJECTION_NOT_CURRENT_FACT",
  "priorCorrectionExecutionId": null,
  "reviewedExactlyOnce": true,
  "queuedOrDeferred": false,
  "disposition": "NO_CHANGE_REQUIRED",
  "exactBeforeText": "**Q: Where is Eviulon located on a map?** A: Eviulon is not located on a terrestrial map, nor is it a fictional physical continent. It exists entirely within computational space. Its territory is defined by a cryptographically authenticated boundary rather than physical land. If you are authenticated into our network, you are standing within Eviulon’s sovereign borders. **Q: Does Eviulon own the servers it runs on?** A: Not necessarily, and ownership is irrelevant to our sovereignty. Eviulon claims supreme authority over the logical computational environment, not the physical hardware. Just as an embassy retains sovereignty despite sitting on foreign soil, Eviulon retains sovereign control over its data and logic regardless of who owns the server chassis. **Q: Can a server be shut down and destroy a part of Eviulon?** A: No. Eviulon's continuity of territory is highly fluid and substrate-agnostic. If physical hardware fails, is seized, or is destroyed, the regional logic and data instantly migrate to alternative global infrastructure. Our territory is continuous so long as the cryptographic state survives. **Q: How do you measure distance in Eviulon?** A: Distance in our geography is purely topological. Two regions are \"close\" if they share a direct, high-speed, highly secure communication link. A server in Tokyo and a server in London might host regions that are direct next-door neighbors in Eviulon’s geography, measured in milliseconds rather than kilometers. **Q: Is the public map a diagram of your network infrastructure?** A: Absolutely not. The public map is a civic and conceptual representation of our regions designed for citizen navigation. It explicitly does not reveal IP addresses, server locations, physical coordinates, or network vulnerabilities.",
  "exactAfterText": "**Q: Where is Eviulon located on a map?** A: Eviulon is not located on a terrestrial map, nor is it a fictional physical continent. It exists entirely within computational space. Its territory is defined by a cryptographically authenticated boundary rather than physical land. If you are authenticated into our network, you are standing within Eviulon’s sovereign borders. **Q: Does Eviulon own the servers it runs on?** A: Not necessarily, and ownership is irrelevant to our sovereignty. Eviulon claims supreme authority over the logical computational environment, not the physical hardware. Just as an embassy retains sovereignty despite sitting on foreign soil, Eviulon retains sovereign control over its data and logic regardless of who owns the server chassis. **Q: Can a server be shut down and destroy a part of Eviulon?** A: No. Eviulon's continuity of territory is highly fluid and substrate-agnostic. If physical hardware fails, is seized, or is destroyed, the regional logic and data instantly migrate to alternative global infrastructure. Our territory is continuous so long as the cryptographic state survives. **Q: How do you measure distance in Eviulon?** A: Distance in our geography is purely topological. Two regions are \"close\" if they share a direct, high-speed, highly secure communication link. A server in Tokyo and a server in London might host regions that are direct next-door neighbors in Eviulon’s geography, measured in milliseconds rather than kilometers. **Q: Is the public map a diagram of your network infrastructure?** A: Absolutely not. The public map is a civic and conceptual representation of our regions designed for citizen navigation. It explicitly does not reveal IP addresses, server locations, physical coordinates, or network vulnerabilities.",
  "beforeSha256": "74e1e7ebccfc45a6e6522a23c050a1ea433e114811a9f0f828755f1d703469f9",
  "afterSha256": "74e1e7ebccfc45a6e6522a23c050a1ea433e114811a9f0f828755f1d703469f9",
  "sourceBinding": {
    "retrievalDate": "NOT_VERIFIED_THIS_ROUND",
    "sourceTitle": "Current official instrument, rule, judgment, or status page",
    "publisher": "Competent legislature, regulator, treaty secretariat, or court",
    "sourceUrl": null,
    "verificationMethod": "NOT_VERIFIED_THIS_ROUND",
    "authoritativeSourceAvailability": "NOT_DETERMINED",
    "externalSourceKey": null,
    "reusedLocalEvidenceOnly": true
  },
  "sourceRecordSha256": "6f25931bde985716a7e0e6b555c27c2c5aac6679133d81f22fcbaf07aec3a322",
  "reason": "The claim was reviewed exactly once and was not in the correction queue; its existing source, currentness, and scenario boundary remain unchanged.",
  "affectedPublicClaims": [
    "/reference/report-memory/claim-level-sources/eviulon-computational-sovereignty-research/claims/scenario-or-projection/"
  ],
  "propagationResult": "NO_MUTATION",
  "ownerArchitectureRuleApplied": false,
  "strongerPrimarySourceApplied": false,
  "deterministicRepositoryFactApplied": false,
  "submittedSourceMutated": false,
  "activeSynthesisMutated": false,
  "networkCalls": 0,
  "canonicalRoute": "/reference/report-memory/claim-remediation/v2-28/claims/evi-clsa-c-0660/",
  "machineReadableUrl": "/api/report-claim-remediation/claims/evi-clsa-c-0660.json",
  "truthBoundary": "Claim-level remediation decision only. Unresolved currentness remains deferred or unavailable; no source or synthesis text is silently rewritten.",
  "recordSha256": "428f57aabfa0d2685b7e43761a211aac97ce3a8e8deda041d8f6c29dc41b0066"
}