Machine Law / immo.quick Core Sovereign Exclusion as Architectural Constraint

Sovereign Exclusion as Architectural Constraint Machine Law / immo.quick Core — Sovereign Exclusion Framework (SEF) v1.0.0 The central compliance failure of modern financial infrastructure is not a lack of rules. It is the absence of a mechanism that enforces those rules deterministically — before consequence, at the execution boundary, with court-admissible proof. This paper introduces the Sovereign Exclusion Framework (SEF): a 9-gate deterministic enforcement architecture that resolves multi-jurisdictional sanctions compliance as a structural property of the system — not as a policy layer added on top of it. The problem addressed is precise: Five major sanctions regimes — OFAC (US), EU restrictive measures, UN Security Council, SECO (Switzerland), and OFSI (UK) — operate simultaneously, with overlapping scope, conflicting jurisdictional reach, extraterritorial obligations, and active blocking statutes. A transaction that satisfies one regime may trigger secondary sanctions exposure under another. An institution that complies with OFAC may violate the EU Blocking Statute (Regulation 2271/96) by doing so. These conflicts do not resolve themselves. They require an architectural decision at T=0. The SEF provides that decision — deterministically. For every transaction, the SEF evaluates all applicable sanctions lists in real time, resolves jurisdictional conflicts through a formal priority stack, and produces one of three verdicts: EXECUTE, DENY, or HOLD. Each verdict is accompanied by a cryptographically sealed proof artifact — an Execution Proof Artifact (EPA) or a Deny Path Artifact (DPA) — that is TEE-attested, WORM-anchored, and designed for regulatory, forensic, and judicial review. This paper provides: — A comprehensive analysis of the international sanctions landscape with country-by-country risk profiles and documented enforcement examples across OFAC, EU, UN, SECO, and OFSI — A formal specification of the conflict-of-laws resolution logic embedded in the SEF gate chain — The complete 9-gate enforcement architecture with predicate definitions, artifact schemas, and jurisdictional binding logic — A rigorous treatment of the financial inclusion question: the SEF excludes nothing that is legally permissible — it enforces what is legally required, and produces proof of both outcomes — An analysis of why existing sanctions screening tools (name matching, list lookups, rule-based filters) are architecturally insufficient under DORA Article 11, the EU AI Act, and analogous operational resilience frameworks The architectural distinction: Conventional compliance systems screen. The SEF enforces. Screening produces a risk score. Enforcement produces a legal verdict with a sealed record. The difference is not operational — it is jurisdictional. A sealed DPA is a legal document. A risk score is an opinion. Sovereign exclusion is not a product feature. It is what happens when the law is compiled into the execution boundary. This paper is the formal specification of that compilation. DOI series: Part of the Machine Law publication record (Concept DOI: 10.5281/zenodo.19301211). Supplements the Machine Law formal framework (10.5281/zenodo.19301212) and the v2.3.0 proof surface specification (10.5281/zenodo.20355497).