Machine Law / immo.quick Core v2.3.0 defines the public technical proof surface for consequence-boundary governance and deterministic institutional enforcement. This record establishes the public-facing evidence base for immo.quick Core v2.3.0: a nine-layer deterministic enforcement architecture designed to prove, at the moment of formation, whether a transaction, decision, or institutional action is legally admissible before any protected consequence can bind. The central problem addressed by this specification is the Boundary-Behavior Gap: the difference between documenting that a process occurred and proving that an impermissible movement could not have produced a consequence. Traditional compliance systems, workflow tools, audit logs, blockchain records, and post-hoc monitoring infrastructures can document process, sequence, signatures, and records. They do not, by themselves, prove that an inadmissible transaction was structurally prevented from becoming effective. immo.quick Core v2.3.0 is specified as a closed-world enforcement architecture: blocked unless formally permitted. Every transaction must satisfy the required admissibility conditions at T=0. If proof does not exist, the system refuses execution and produces a Deny Path Artifact (DPA). If all conditions are satisfied, the system produces an Execution Proof Artifact (EPA), a cryptographically bound proof object designed for institutional, regulatory, forensic, and judicial review. This DOI record contains two complementary documents: 1. Public Technical Proof Surface A sanitized technical proof document describing the public verification model, proof-object structures, deterministic refusal logic, EPA/DPA schemas, admissibility predicates, bi-temporal evidence model, zero-knowledge proof doctrine, governance divergence logic, and verification methodology. 2. Institutional Specification A broader institutional architecture document describing the full technical, legal, sectoral, geopolitical, and economic framing of immo.quick Core v2.3.0, including the NDA-gated access model for qualified institutions, regulators, governments, central banks, auditors, and authorized examiners. Together, these documents define the public proof surface and the protected institutional verification boundary. The public proof surface is intentionally designed to be sufficient for public category evaluation, architectural understanding, and regulatory-facing explanation without disclosing the protected production substrate. It explains what is proven, how proof objects are structured, how refusal is represented, how replay and verification are conceptually performed, and why public proof does not require public leakage. This record does not disclose production keys, private cryptographic material, customer payloads, live system endpoints, operational credentials, production node topology, exact quorum configuration, productive registry locations, enforcement adapter logic, institution-specific policy bundles, proprietary source code, or security-sensitive implementation details. All hash values, Merkle roots, PCR values, BFT quorum parameters, epoch identifiers, attestation objects, and proof samples included in the public technical document are illustrative structural examples derived from synthetic test payloads. They demonstrate the schema, format, and verification posture of production artifacts without exposing exact production values or operationally exploitable infrastructure details. The distinction is deliberate: Public proof is not public leakage. The public receives the proof surface. Qualified institutions receive the verification layer. The protected production substrate remains available only under lawful institutional standing, binding NDA, and institutional verification. The architecture specified in this record includes: - deterministic consequence-boundary governance;- Prior Admissibility Space (PAS);- Deny Path Artifact (DPA);- Execution Proof Artifact (EPA);- Deterministic Execution Proof Engine (DEPE);- Bi-Temporal Ledger (BTL);- Exogenous Anchor Protocol (EAP);- Sensor/Oracle Trust Bridge (SOTB);- Machine Law Engine (MLE);- Regulatory Intent Preservation (RIP);- Cross-Jurisdictional Portability Layer (CJPL);- Autonomous Regulatory Examination Engine (AREE);- Governance Logic Divergence Engine (GLD);- post-quantum signature posture;- zero-knowledge proof based selective disclosure;- identity-first access and refusal semantics;- institutional verification without public system exposure. The public proof surface is designed to satisfy the legitimate public interest in understanding how consequence-boundary governance works while preserving the confidentiality, resilience, and security obligations expected under DORA, NIS2, the EU AI Act, GDPR, and comparable cybersecurity, operational-resilience, and institutional-risk regimes. The purpose of this record is therefore not to expose a live system. It is to anchor the public technical proof surface for a new institutional category: Machine Law. Machine Law means that admissibility is not merely reviewed, monitored, or documented after the fact. It is compiled, evaluated, enforced, refused, attested, and proven before consequence. This record establishes the public evidence base for that architecture. The live enforcement system, production artifacts, regulator-grade examination packages, cryptographic materials, node infrastructure, and protected execution substrate remain NDA-gated and available only to qualified institutional parties under verified access. Public proof surface, not production substrate.
Rami Cherri (Sat,) studied this question.