{
  "id": "EVI-RCSR-230-0206",
  "slug": "evi-clsa-c-0316-0206",
  "title": "Source research for EVI-CLSA-C-0316",
  "dependencyId": "EVI-CDEP-229-0206",
  "claimId": "EVI-CLSA-C-0316",
  "reportId": "REP-INFO-RIGHTS-001",
  "claimClass": "STANDARDS_VERSION_CLAIM",
  "previousDisposition": "DEFERRED",
  "researchDisposition": "DEFERRED",
  "sourceKey": null,
  "sourceUrl": null,
  "publisher": null,
  "sourceTitle": null,
  "publicationOrUpdateDate": null,
  "accessDate": "2026-08-09",
  "jurisdiction": "Competent legislature, regulator, treaty secretariat, or court",
  "claimSupported": "NOT_ESTABLISHED",
  "limitations": "No sufficiently specific current primary source was identified in the bounded source batch.",
  "currentness": "UNAVAILABLE",
  "exactBeforePassage": "Eviulon’s public-record access process is modeled upon responsive, time-bound freedom-of-information regimes, most notably the Illinois FOIA (5 ILCS 140), adapted for the velocity of a machine state \\[VERIFIED EXTERNAL LAW\\]. The access-request lifecycle begins when a query is submitted via a standardized API or human-readable portal \\[PROPOSED EVIULONIAN RULE\\]. Identity requirements vary based on the classification of the requested data; while anonymous requests are fully permitted for PUBLIC records, accessing CONTROLLED or PERSONAL records requires absolute cryptographic authentication. Upon receipt, the state must conduct a reasonable and thorough cryptographic search of the relevant databases. Acknowledgment of the request must be transmitted within a brief, statutory timeframe, providing the requester with a tracking hash and an estimated completion metric. Standard requests must be fulfilled rapidly—typically within five computational cycles4. However, if a query encompasses a massive volume of unstructured data that threatens to degrade operational network performance, it may be designated a \"voluminous request,\" triggering an automatic extension of the timeline and requiring the requester to narrow their scope6 \\[COMPARATIVE PRACTICE\\]. When a requested record contains a mixture of exempt and non-exempt data, Eviulon enforces a strict doctrine of segregability. The exempt data must be redacted, and the remaining partial release must be delivered to the requester4 \\[VERIFIED EXTERNAL LAW\\]. In the event of a total or partial denial, the state must explicitly cite the statutory exemption applied and provide the algorithmic output of the public-interest balancing test6. While access to digital records is fundamentally free to ensure democratic participation, automated API rate-limit extensions for massive commercial bulk pulls may require the expenditure of Compute Credits \\[ANALYST RECOMMENDATION\\]. Any denial may be appealed directly to the Information Review Authority. Concurrently, any record released through this reactive process is simultaneously logged and published in a global disclosure repository, ensuring equal access for all citizens \\[PROPOSED EVIULONIAN RULE\\]. To alleviate the administrative burden of reactive requests, Eviulon relies heavily on a proactive-publication framework. Proactive transparency eliminates the friction of access and reinforces institutional trust \\[PUBLIC-INTEREST PRINCIPLE\\]. The State Registry is constitutionally mandated to continuously and automatically publish binding laws, administrative decisions, state budgets, compute expenditure logs, procurement contracts, non-sensitive topological datasets, assurance records, correction notices, and public service standards \\[PROPOSED EVIULONIAN RULE\\]. Because Eviulon is a machine state, its primary interface for transparency is programmatic. Public APIs are governed by stringent rules regarding data minimization; endpoints return only the specific data requested, preventing the accidental leakage of adjacent metadata \\[PROPOSED EVIULONIAN RULE\\]. Rate limits are strictly enforced to protect against denial-of-service attacks and bulk data abuse, though these limits can be scaled for verified academic and accountability researchers. Furthermore, as state protocols evolve, API versioning ensures continuity. Deprecated APIs are preserved as functional archival snapshots, guaranteeing that historical data retrieval methods remain reproducible for future auditing \\[ANALYST RECOMMENDATION\\].",
  "beforeSha256": "67deb09ce85d147b40b86708ad83ab5b0d6589bbf069fa1f92d84b7bd938308a",
  "proposedAfterPassage": "The claim remains deferred or unavailable pending a sufficiently specific current primary source and an authorized append-only correction decision.",
  "afterSha256": "fdff3cdcefae7fb7102f75925ab131d328df7f06853039a68cbdf4c280ed6cd9",
  "correctionNoticePublished": false,
  "correctionAppliedToSource": false,
  "correctionAppliedToActiveSynthesis": false,
  "submittedSourceMutated": false,
  "activeSynthesisMutated": false,
  "publicExplanation": "No sufficiently specific current primary source was identified in the bounded source batch; the claim remains unavailable or deferred.",
  "automaticApplicationProhibited": true,
  "reviewedExactlyOnce": true,
  "repositoryRuntimeNetworkCalls": 0,
  "canonicalRoute": "/reference/report-memory/source-research/v2-30/records/evi-rcsr-230-0206/",
  "machineReadableUrl": "/api/report-claim-source-research/records/evi-rcsr-230-0206.json",
  "truthBoundary": "Claim-level source-research record. A citation supports only the bounded proposition identified here. Submitted source bytes and active synthesis remain unchanged; correction notices append history and do not silently rewrite reports.",
  "recordSha256": "1e4028e798e088bc0ac992c0a88071907503924cd4292790d5d9a08f044bd78a"
}