Language:
GLOBAL REGULATORY CONVERGENCE

The world is moving toward execution.

FINMA, BaFin, the EU, NIST, NSA and U.S. government strategies are converging on continuous authorization, Zero Trust, resilience, evidence, accountability and enforceable boundaries. See source by source how immo.quick already unifies these control properties in a deterministic Execution Rights architecture — and where Machine Law goes further.

Open official comparison →How Execution Rights work →
PRODUCTS▾
Home Core Serverless EditionHealthcare Why It’s DifferentExecution RightsGlobal Requirements CDS — Constitutional Screening STFL — Sovereign Transaction Finance Layer Verify Security All Gates
SECTORS▾
All SectorsHealthcareDefenceAviationHeavy IndustryFinancial MarketsAsset Management & Securities FinancingPharma & Clinical TrialsLogisticsSport & MotorsportMusic & Digital MarketsEnergy & ESGPublic SectorSociety & AdministrationAI · Data · Cyber · TelecomReal Estate & TransactionsAgriFood & Food Safety
MORE▾
ASSURANCE
Authority Surface Execution RightsOverride Accountability Capabilities Authoritative Sources Evidence Evidence Registry Fortress Baseline Adversarial Verification Machine Law Evolution
SOLUTIONS
Institutions Regulators Governments Investors · PE Jurisdictions Due Diligence
RESOURCES
Facts Press Newsroom FAQ Machine Law Gate SDK Public Documentation The Sound of Machine Law
COMMERCIAL
Pricing
Quantum Security 🔍 Search Request Access →
VERIFY · ERI AUDITS · EXECUTION RIGHTS INFRASTRUCTURE

DO NOT TRUST THE CLAIM. AUDIT THE EXECUTION PATH.

The Execution Rights Infrastructure is designed so that domain logic may determine conditions, but cannot grant itself execution authority. These two audit runs test two different questions: first, whether the core invariants resist adversarial manipulation; second, whether governed execution paths can bypass the universal Spine at all.

113/113CURRENT AUDIT · PASSED
39/39GLOBAL ENFORCEMENT · PASSED
0BYPASS PATHS DETECTED IN TESTED SCOPE
NO VALID EXECUTION RIGHT. NO CAPABILITY. NO EXECUTION.
TWO AUDITS · TWO QUESTIONS
AUDIT 01 · 22:10:34Z

Adversarial Core Conformance

74/74

This first run attacks the ERI primitives and invariants themselves. It tests whether capabilities can be forged, closure bypassed, state raced, the dependency graph poisoned, invariants mutated, or the public manifest contradicted by runtime behavior.

  • 6 suites
  • Capability Forgery
  • Closure Bypass
  • Revocation Race / TOCTOU
  • Graph Poisoning
  • Invariant Mutation
  • Manifest / Runtime Conformance
→
AUDIT 02 · 23:36:32Z

Global Enforcement & Bypass Audit

113/113

The second run keeps the adversarial core suites and adds the missing system-level question: can any governed execution path get around the Spine, Closure, Capability, Consumption or Point-of-Execution revalidation?

  • 7 suites
  • 39/39 Global Enforcement tests
  • 0 bypass paths detected in tested scope
  • Direct execute without capability: blocked
  • Fake or non-Spine capability: blocked
  • Legacy PASS → execute: blocked
  • Replay attack: blocked
  • Simulation → production: blocked
WHAT CHANGED BETWEEN THE AUDITS?
QuestionAudit 01Audit 02
Do the ERI invariants hold under attack?Yes · 74/74Reconfirmed
Can a gate define EXECUTE / AUTHORIZED?RejectedRejected system-wide
Can 4/5 closure dimensions issue a capability?NoNo
Can consumed / revoked / expired capabilities execute?Blocked by core checksBlocked at the governed execution path with precise failure semantics
Can an execution path bypass the Spine?Not the scope of the first run0 bypass paths detected
Can a directly created capability execute without Spine issuance evidence?Not yet tested globallyNo · SPINE_ISSUANCE_REQUIRED
INCORRUPTIBLE EXECUTION LOGIC

The system cannot be persuaded to make an exception.

“Incorruptible” is used here in the architectural sense: a gate, user, AI component or domain module cannot turn a determination into execution authority by wording, confidence, privilege or convenience. A governed execution requires current Authority, Rule, Jurisdiction, Time and Dependencies, a Spine-issued capability, and a valid execution-boundary check.

PASS is not permission. Authority is not inferred. A capability is not accepted because it looks valid. The execution path must prove its right to execute.
Claim boundary: This is technical adversarial conformance evidence for the tested implementation and tested scope. It is not a claim that software is impossible to compromise, not a third-party security certification, and not proof that an external source or real-world fact is substantively true.
WHAT THE SERVERLESS EDITION CAN NOW ENFORCE
Determination ≠ AuthorizationDomain gates can say PASS, BLOCK, WARN or OUT_OF_SCOPE, but cannot create execution authority.
5-Dimensional Rights ClosureAuthority, Rule, Jurisdiction, Time and Dependencies must close before a capability may exist.
Spine-Issued CapabilityA directly created or fake capability cannot cross the execution boundary without valid Spine issuance.
Replay Attack ProtectionA consumed capability cannot be used for a second execution; legitimate idempotent retry returns the prior result.
Point-of-Execution RevalidationRevoked authority, stale dependencies, wrong executor or environment mismatch block at the boundary.
State-Bound EvidenceExecution evidence remains bound to the state, capability and execution path that produced it.
Change ImpactDependency relationships expose which downstream determinations, capabilities and executions are affected by changed state.
Simulation IsolationSimulation capabilities remain suspended and cannot become production execution rights.
Runtime / Manifest ConformancePublished architecture claims are checked against runtime enforcement rather than left as documentation-only statements.
RAW EVIDENCE

Both audit reports remain independently inspectable.

Audit 01 · Adversarial Core Conformance · 74/74SHA-256 a00db5f7d95f53963eba60b51cbb646a7d61131688ff89e3daf3bb21d6e00bf8Audit 02 · Global Enforcement · 113/113 · 0 bypass pathsSHA-256 e6b8a203dd6ae965736b56ecc441aadd1472c25e24642bd5b5295e20a0d9fb30← Back to Verify
INSTITUTIONAL PROOF PATH
Global RequirementsExecution RightsAuthorization LogicAuthority SurfaceVerifyClaim Boundaries
Request Access →