◎ OS PUB Apache 2.0 ← All specifications

P188 — AIEP — Evidence Jurisdiction-Aware Access Protocol

Publication Date: 2026-04-12 Status: Open Source Prior Art Disclosure Licence: Apache License 2.0 Author/Organisation: Phatfella Ltd Schema: AIEP_OS_SPEC_TEMPLATE v1.0.1 — https://aiep.dev/schemas/aiep-os-spec-template/v1.0.1

Field of the Invention

[0001] The disclosure relates to jurisdiction-aware access and routing mechanisms for evidence artefacts in computing environments.

[0002] More particularly, the disclosure concerns an evidence jurisdiction-aware access protocol for use within an Architected Instruction and Evidence Protocol (AIEP) system, ensuring that evidence artefacts carrying jurisdiction restrictions are only accessed, processed, and stored within infrastructure that satisfies applicable territorial data-processing requirements.

Framework Context

[0003] This invention operates within an Architected Instruction and Evidence Protocol (AIEP) environment as defined in United Kingdom patent application number GB2519711.2, filed 20 November 2025, the entire contents of which are incorporated herein by reference.

Summary of the Disclosure

[0004] A computer-implemented evidence jurisdiction-aware access protocol comprises: tagging each evidence artefact with a JurisdictionConstraintSet comprising one or more JurisdictionCodes (e.g., UK-GDPR, EU-AI-ACT, US-HIPAA) and a DataResidencyRegion; maintaining a NodeJurisdictionProfile for each AIEP deployment node declaring the node’s declared_legal_jurisdiction and data_residency_regions; before routing an evidence artefact to a remote node for processing or storage, evaluating a JurisdictionCompatibilityCheck between the artefact’s JurisdictionConstraintSet and the target NodeJurisdictionProfile; rejecting transfer when JurisdictionCompatibilityCheck returns INCOMPATIBLE and generating a JurisdictionBlockRecord containing target_node_id, artefact_id, incompatible_constraint_ids, and block_timestamp; logging all jurisdiction-compatible transfers as JurisdictionTransferAuditRecords; and preventing local processing agents from loading artefacts with a JurisdictionCode requiring explicit legal-basis authorisation unless a valid LegalBasisAuthorisationRecord is present in the evidence store.

[0005] JurisdictionConstraintSets cannot be removed at runtime — only the addition of further constraints is permitted.

[0006] The technical effect is modification of computing system behaviour by enforcing jurisdiction-aware evidence routing at the data-plane level, providing machine-verifiable territorial compliance for multi-jurisdiction deployments.

Claims

[0007] A computer-implemented method for evidence jurisdiction-aware access management comprising: tagging evidence artefacts with JurisdictionConstraintSets; maintaining NodeJurisdictionProfiles; evaluating JurisdictionCompatibilityChecks before cross-node transfers; generating JurisdictionBlockRecords on incompatible transfers; maintaining JurisdictionTransferAuditRecords; and requiring LegalBasisAuthorisationRecords for restricted jurisdiction codes.

[0008] A system for evidence jurisdiction-aware access management comprising one or more processors and a non-transitory computer-readable medium storing instructions to execute the method of claim 1.