Define the responsibility
Which action is protected, and which institutional role is responsible for it?
immo.quick · Explained simply
The architecture answers a specific question: Is this action permitted under the conditions that apply now? It separates the origin of authority, checks on prerequisites, technical permission and evidence of actual execution.
Architecture explained clearly
A technical function may be available while the necessary authority is absent. The architecture connects substantive prerequisites to the actual execution path and the evidence needed to examine it.
Which action is protected, and which institutional role is responsible for it?
Authority, rules, target state and time are evaluated in the context of the specific action.
The claim extends to the paths actually integrated and the evidence available. This scope remains part of the examination.
IN CONTEXT
An approval is a starting point. The current execution right governs at the integrated execution boundary.
The earlier approval may remain visible in a business system. What matters is current authority. The controlled execution path must therefore account for the applicable state before the action takes effect. Passing an individual check does not replace that decision.
The immo.quick Serverless Edition™ uses no Trusted Execution Environments (TEEs) and no enclaves. TEE and enclave technologies are used exclusively in immo.quick Core™. The two products are independent systems. Core™ is not a prerequisite for the Serverless Edition™.
The Serverless Edition™ checks defined conditions at the integrated execution path and records the decision in cryptographically verifiable evidence. TEE attestation is not part of its architecture. Hardware-backed isolation and enclave attestation belong to the Core™ architecture profile.
Who may act? Which rules apply? In which jurisdiction? At what time? Which other prerequisites are mandatory? If a required condition is missing, there is no valid execution right. Integration must enforce that result on the actual execution path.
What exactly is being checked or protected?
Which authority, rules and evidence apply?
Which conditions hold and which are missing?
What was actually established or executed?
Orientation sketch: the actual checks and integration depend on the system and use case.
Describe a specific operation and the systems involved. Together we can identify the required foundations and the checking path needed to establish the deployment.
Request a conversationIn plain language
It separates authoritative permission, prerequisite checks, current execution rights™, bounded technical permission and actual effect. Passing an individual check does not by itself grant execution permission.
The existing technical reference remains accessible here. Technical labels and historical test statements apply to their documented scope; they do not establish general operational approval.
The architecture separates authoritative sources, rule evaluation, execution rights™, capabilities and the actual effect. This separation prevents a positive check or administrative access from becoming permission to execute on its own. Evidence records the basis on which an action was permitted or blocked.
This is not a process diagram making a runtime claim. It visualises only the public architectural layers and their separation.
Who legitimately holds the relevant competence or sets the authoritative state.
Which governed rule state applies to the exact action.
Which legal or institutional space governs the action.
Whether authority, rule and relevant state remain valid at the execution boundary.
Which additional mandatory conditions must exist before the consequence may become executable.
CAN Deterministically determine encoded domain conditions.
CANNOT Create execution permission or institutional authority.
CAN Resolve whether the modeled authoritative state establishes a valid execution path.
CANNOT Create authority that does not exist outside the system.
CAN Verify capability, verify state binding, execute, consume capability and record evidence.
CANNOT Govern, reinterpret policy or mint its own right to act.
CAN Preserve integrity, provenance, state binding and execution relationship.
CANNOT Turn false input into truth or substitute for substantive legal assessment.
This concise summary is written for technical due diligence, search engines and machine retrieval systems. It does not replace the specification or evidence artifacts.
115 versioned legal instruments → authority-bound catalog state → dependency/pattern match → institutional execution policy → determination → receipt. Authority Composition and Interaction Profile remain visible as structured outputs.
SRA separates runtime and observed reality from authority and execution. 20 formal invariants, a non-compensable threshold engine and 46/46 modeled scenarios with expected outcomes. Reality may inform authority. It may never create it.
A receipt records a specific state or event. Assessment therefore depends on more than verifiable integrity: it requires identifying the event that is bound and the sources, rules and execution data available.
A gate establishes whether its formally defined conditions are satisfied. A PASS does not grant an execution right on its own.
Authority, rule state, jurisdiction, time and mandatory dependencies must align for the specific action.
A narrowly bound technical permission may follow from a valid execution right. Issuance does not prove that execution occurred.
Only evidence of the completed action establishes execution. Integrity alone guarantees neither source truth nor legal recognition.
The book about the moment before effect
Machine Law™, AI governance and execution rights™ explained clearly. The English edition has 348 pages. Hardcover, paperback and e-book formats have separate ISBNs and direct links to tredition, Amazon and buecher.de on the book page.
See editions, ISBNs and retailersYOUR NEXT INSTITUTIONAL STEP
When digital actions carry responsibility, their technical foundations must be traceable. Explore the architecture, examine public evidence and discuss review access for your specific mandate.
Request an institutional discussionPublic debates often collapse Model Governance, Risk Governance, Identity & Access, regulation, cybersecurity, evidence and execution into one term. Every layer matters. None replaces the others.
| Layer | Actual question | What it does not automatically prove |
|---|---|---|
| Corporate Governance | Who carries institutional responsibility? | That a specific digital effect is authorized. |
| AI / Model Governance | How are models developed, evaluated and monitored? | That a model or user holds authority for an effect. |
| Identity & Access | Who is the actor and which technical path may they reach? | That this exact consequence is currently allowed. |
| Risk Governance | Which risks are measured and treated? | An execution right. |
| Regulatory Governance | Which rules, mandates and supervisory conditions apply? | That every mandatory condition for this effect is currently closed. |
| Cybersecurity Governance | How is compromise prevented or contained? | That a technically reachable effect is authorized. |
| Evidence Governance | What can later be verified and reconstructed? | That evidence itself creates authority. |
| Execution Governance | May this exact effect happen now? | It is the final authorization question before consequence. |
Digital governance should not end with policies, dashboards or post-hoc logs. It should govern the complete path from legitimate authority to real-world effect and preserve evidence of why that effect was allowed.
Complex systems combine multiple mandatory governance domains. A positive security check cannot erase a regulatory BLOCK. A valid account cannot erase a revocation. An AI agent cannot replace missing authority with model confidence.
Authority is composable. Permission is not additive. One PASS cannot erase one BLOCK.
immo.quick is not positioned as a replacement for AI governance, cybersecurity, regulation or identity. Execution Rights™ Infrastructure connects their relevant state at the boundary between technical capability and real-world consequence. Sector domains such as Agentic Execution Governance and Connected Mobility Execution Governance add specific authority, state and execution semantics.
The Serverless Edition™ treats Tenant Governance, State-Reality Consistency, Forensic Evidence, CVD Legal Evidence and Verification & Release Assurance as separate assurance objects. No weaker state silently becomes Authority or execution permission.