Regulated machines should not execute because a model, workflow or administrator says yes. Technical executability should exist only when a valid execution right exists under the authoritative state.
AI, data, policies, scores, humans and gates may determine or analyse state. None of them independently creates execution authority.
Determination may inform the state. It does not create permission.
Execution authorization with additional hardware-rooted assurance where the deployment architecture calls for it.
Hardware-independent architecture. Infrastructure may vary. Authority does not.
Neither architecture is a deployment variant of the other. Core was the origin. Serverless is an independent evolution of the same architectural thought.
Regulation, mandates and other legitimate authoritative sources determine the normative state. immo.quick does not create that authority. It deterministically establishes whether that state creates a valid technical right to execute and preserves the resulting execution as cryptographically verifiable evidence.
This is an institutional systematic, not a hard execution-dependency chain. Each layer remains independently deterministic.
The Gate Catalog spans regulatory, institutional, sector-specific and infrastructure-level domains. Each Gate performs deterministic Domain Determination. No Gate independently grants Execution Authority. Authoritative rules define the conditions. The Execution Rights Graph resolves whether a valid right to execute exists. The Execution Plane decides nothing.
Why classical compliance thinking is no longer sufficient, and what changes instead.
Why It’s Different →Across Authority, Rule, Jurisdiction, Time and Dependency.
No probability. No escalation. No retrospective control.
Explore execution authorization →The ledger begins when you deploy it. Yesterday cannot be cryptographically recreated tomorrow.
Chain active since June 2026 →The question is not whether you have logs. The question is whether you have proof.
Request institutional access →immo.quick publishes technical claims with scope, evidence class and an explicit boundary. A public statement should not silently become stronger than the artifact that supports it.