INSTITUTIONAL TRUST INFRASTRUCTURE

Who is accountablewhen your AI acts?

Autonomous AI can initiate payments, share data and trigger operational processes. Your institution needs control over the authority under which this happens. immo.quick develops institutional trust infrastructure that connects control and verifiable evidence to the specific action.

Authority must be technically enforced before an action takes effect.

immo.quick Core™ immo.quick Serverless Edition™

Daylit institutional architecture with natural stone, glass and people in conversation.
immo.quick brand seal · Trust by Design, Impact by Architecture
Institutional technology. Designed with responsibility.AI-generated architectural image

THE DECISIVE QUESTION BEFORE AN ACTION TAKES EFFECT

Technical capability does not establish authority to act.

A login identifies the user. An approval records a decision. When a system acts autonomously, what matters is the current authority for that specific action. The immo.quick Serverless Edition technically checks this at execution points that are actually integrated.

Current authority

Who may perform this specific action under the conditions that apply now?

Control at the point of execution

Before the protected action takes effect, the bound Execution Right is checked for validity.

Verifiable result

The receipt binds the evaluation basis and result. Missing evidence and boundaries remain explicit.

Control requires integration of the protected execution path and availability of the authoritative state data. Eligible prospective customers, investors, buyers and auditors can examine the actual scope and its boundaries through internal Live Due Diligence.

BEFORE AN ACTION TAKES EFFECT

Your next critical action will not wait for your next audit report.

A payment leaves your institution. Confidential data is released. An agent initiates an operation. If the underlying authority has changed, the control immediately before the effect becomes decisive. This is where the immo.quick Serverless Edition applies.

What your institution clarifies today need not be reconstructed at the decisive moment.

THREE MINUTES. ONE DECISIVE BOUNDARY.

The approval exists. The authority no longer does.

An illustrative case: At 16:44, the relevant authority is revoked. At 16:47, a previously approved payment is due to execute. The historical approval status does not yet answer the decisive question.

  1. 16:44 · STATE CHANGED

    The basis falls away.

    The approval remains visible. Its underlying prerequisite has changed.

  2. 16:47 · BEFORE THE EFFECT

    Current authority matters.

    A valid execution right for this specific action must exist at the protected execution boundary.

No valid execution right. No execution.

Illustrative case, not a real transaction. Enforcement applies to integrated execution paths and requires the authoritative state data.

Understand Execution Rights →

IMMO.QUICK

Two systems for institutional responsibility.

Choose the starting point that fits your task. Each system has its own architecture profile and a clearly defined object of review.

immo.quick Serverless Edition™ · Original logo

immo.quick Serverless Edition™

Control execution rights at the point of effect.

Serverless Edition binds the actor, action, target, relevant state and time to an execution right. At the protected boundary, it checks whether that specific action may execute.

Explore the system
immo.quick Core™ · Original logo

immo.quick Core™

Make institutional decisions traceable.

Core binds institutional findings to their formation context and evidenced execution environment. Hardware-backed isolation and attestation form part of its own trust architecture.

Explore the system

IMMO.QUICK SERVERLESS EDITION

From authority to traceable execution.

Serverless Edition connects the prerequisites for a protected action to enforcement at the actual execution point and the supporting evidence.

  1. Authority

    Who may perform which specific action, and under what conditions?

  2. Evaluation

    Required rules and evidence are evaluated within the relevant context.

  3. Execution

    The execution right is checked at the protected point of effect.

  4. Evidence

    A cryptographically bound receipt records the evaluated decision for subsequent review.

Understand Execution Rights

INTERNAL LIVE DUE DILIGENCE · IMMO.QUICK SERVERLESS EDITION

Examine the substance. Trace the results.

Controlled internal review access makes Serverless Edition examinable for prospective customers, investors, buyers and auditors. The four specialist modules Cyber DD, OPS-DD, DSGVO-DD and KI-DD connect 140 mandatory declarations across 40 check domains to deterministic evaluation and sealed receipts.

INSTITUTIONAL CONTEXTS

The right perspective for your mandate.

Across operations, care, financial transactions and public administration, the focus is the specific action and the authority supporting it. Explore the institutional contexts in detail.

Explore all 21 sector contextsAI-generated institutional illustrations.

FORM YOUR OWN VIEW.

Ask to see the boundary. And the evidence behind it.

An institutional decision needs more than a persuasive presentation. Prospective customers, investors, buyers and auditors can request controlled internal review access to examine what the system does, which foundations are available and where its limits lie.

4
specialist modules
40
check domains
140
mandatory declarations

Cyber DD · OPS-DD · GDPR-DD · AI-DD

These numbers describe the catalog of the four specialist modules. They are not a blanket certification of an institution.
OUT NOW

Now available · German and English

Der Moment davor / The Moment Before

Hardcover, paperback and e-book at tredition.

Der Moment davor · Rami CherriThe Moment Before · Rami Cherri

EXPLORE IN DEPTH

A clear overview. The substance remains accessible.

Open the area relevant to your review. All detailed explanations and existing content remain available here.

Architecture and institutional controlSystem boundaries, integration and concrete execution examples.

immo.quick develops trust infrastructure for institutions that need to control digital actions and make decisions traceable. Two independent systems combine technical substance with clearly defined authority and verifiable evidence.

The moment between approval and effect.

Between approval and execution, authority and conditions can change. “The approval was valid. Is it still valid now?” describes that boundary. Serverless Edition checks the execution right for the specific action at the protected point of effect.

Two systems. Clear architecture boundaries.

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.

immo.quick Serverless Edition™ · immo.quick Core™

Original home screens of immo.quick Core on the left and immo.quick Serverless Edition on the right, displayed on two monitors within an AI-generated setting.
Two independent systems, shown together. Original home screens of immo.quick Core and immo.quick Serverless Edition, presented within an AI-generated setting. Tap or click to enlarge.

What may your software do at this moment?

A payment, a data transfer or an AI action may be technically possible yet no longer permitted. immo.quick connects applicable authority and prerequisites to the specific action. The Serverless Edition™ addresses protected execution. The independent Core™ system makes the origin of institutional checking results traceable.

The Moment Before

Three minutes that change everything.

  1. Earlier

    A payment is approved. The authorized signatories have signed.

  2. 4:44 p.m.

    A board resolution revokes the governing authority. The earlier approval remains visible in the system.

  3. 4:47 p.m.

    The payment is about to leave the bank. What matters now is whether a valid execution right exists.

Model case from “The Moment Before”, not a real bank transaction. The Serverless Edition™ operates at the controlled effect boundary. The protected action and its execution paths must actually be integrated.

WHY CONVENTIONAL SYSTEMS ARE NOT ENOUGH

Why access alone is not enough.

Conventional IT and security systems remain essential. IAM checks identity and access, workflows coordinate processes, SIEM detects anomalies, risk engines assess risk and audit logs document events. These systems solve different problems.

The additional question is: may this specific action execute under the authority and rules that are valid now? Passing an individual check is not a complete execution right. SaaS describes a delivery model; the decisive issue is whether binding control sits in the actual execution path.

System
Answers
immo.quick
IAM / Login
Who is the user?
Identity is part of the decision, not complete authority.
Workflow
Is the process formally correct?
A correct process is not automatically institutionally permissible.
SIEM / Monitoring
Is there suspicious activity?
Detects risks but does not by itself decide whether the action is permissible.
Risk Scoring
How high is the risk?
Risk assessment is not authorization.
immo.quick
May the action be executed — now?
Binds authority, rules, jurisdiction, time, dependencies and context into a deterministic decision.

immo.quick

Two independent systems. One clear overview.

immo.quick Core™

Technically bind determination and causality

Core™ binds an institutional determination to its governing state, its foundations and the evidenced execution environment. Hardware-backed isolation and attestation form part of its own trust architecture.

Understand Core™ →

immo.quick Serverless Edition™

Control execution rights™ before effect

Serverless™ integrates with existing applications and execution paths. It binds actor, action, target, governing state and time to an execution right and revalidates that right at the protected effect boundary.

ACES™: a closed domain for selection and fitness evidence within Serverless™.

Understand Serverless™ →

Core™ and Serverless™ are independent systems. This overview shows their responsibilities, not a technical dependency between them.

immo.quick Serverless Edition™ · ACES™

ACES™: rules that cannot be bypassed.

Whoever carries a service weapon, looks after children or treats patients needs valid evidence. ACES™ makes sure fitness and reliability evidence takes effect at the decisive moment, and that personnel selection is fair, justified and decided by people. No blacklists, no diagnoses, no automatic exclusion.

17 sector templatesGermany · EU · USA · CanadaA receipt for every step
Understand ACES™ →
ACES™
HOW THE SERVERLESS EDITION™ CONNECTS

Integrate the control boundary into existing systems.

The integration method may vary. The decision and evidence semantics must not. API, event, workflow, agent, controlled offline transfer or hybrid operation are different transport and integration patterns for the same institutional control question.

Onboarding in detail →
01 · REQUESTIdentify actor, action, target and purpose
02 · BASISBind authority, rule state and jurisdiction
03 · EXECUTION RIGHTResolve time and mandatory dependencies
04 · EXECUTIONRevalidate and consume the bound capability
05 · EVIDENCERecord the decision and observed effect

Implementation begins by defining which actions actually require protection. Authority sources, internal and external data, relevant jurisdictions and rule domains are then mapped. Only then is the technical control boundary connected to the actual Point of Effect and validated with positive and adversarial negative tests.

SECTORS

Governance in the context of your sector.

Each sector has its own regulatory, operational and technical requirements. Relevant gates, legal rules and data sources are therefore explained within the sector context rather than as an isolated gate catalogue.

View all sectors →
JURISDICTIONS AND LAW

Resolve jurisdictions and rules in context.

immo.quick does not treat jurisdiction as a static country field. Rules can overlap or conflict. Such collisions are not silently averaged away; they become explicit states and are routed into a defined governance path.

Explore jurisdictions →
EUGDPR · DORA · MiCA · EU AI Act
Collision screening
DEGwG · KWG · WpHG · AWG/AWV
National + EU context
USOFAC · Export Controls · sector rules
Cross-border checks
CH / UK / INTFINMA · DSG · FCA · FATF
Context-dependent activation
◎
Globally applicableLegal spaces, sectors and standards in a consistent decision model.
✓
Traceable & verifiableMachine-readable rules, traceable states and evidence paths.
▱
For critical infrastructureDesigned for environments with high regulatory density and complex dependencies.
TENANT OPERATING MODEL · FINALIZED

Finalized Tenant Operating Model

30 primary actions. Attention-first. File-first intake. Permissions, decisions, receipts and integrations in one operating logic – with the authority boundary unchanged.

Explore the Tenant Operating Model →
Verification and evidenceReceipts, Negative Assurance and public review paths in context.

NEGATIVE ASSURANCE™ · SERVERLESS EDITION™

“No results” is not yet reliable evidence.

Was a defined emergency path used? Does the captured period contain a particular event class? Are the required erasure records present? Negative Assurance™ examines these questions against defined sources and records the result, coverage and limits together. Missing relevant data prevents a positive attestation.

The difference matters when the next audit question arrives. You can present the examined dataset, period and basis of your answer. The capture must be in place beforehand. A gap discovered at the review cannot simply be repaired with a more persuasive report.

ABSENCE

An event class is absent

Examines whether a precisely named event class is present in the captured records for a defined period. The absence of an event label does not establish that a real-world action never occurred.

NON_OVERRIDE

Examine defined exception paths

Examines the override and emergency paths expressly defined in the profile. Ordinary human decisions, refusals and revocations are not automatically overrides. The statement is limited to the paths and data actually covered.

ERASURE

Check erasure evidence

Examines whether required destruction records exist for specified data and keys. This does not automatically establish complete deletion or the irrecoverability of every copy and backup.

Absence of an event class in the examined dataset, not blanket absence of real-world actions. Origin verification currently requires the key holder.

Read the explanation. Examine the evidence.

What does the system check? Which rules apply to an institution? What record is produced? These public entry points connect capabilities to concrete review paths. Journalists and investors can examine the same foundations, explained in plain language.

CDS™

Screen legal texts against encoded constitutional and fundamental-rights patterns. Findings and rule versions make the result traceable.

Understand CDS™

STFL™

Connect a review event to its accounting record. A shared reference makes it possible to trace what was billed and why.

Understand STFL™

Internal Deterministic Live Due Diligence™

The system provides a deterministic account of its own defined architecture and evidence state.

Explore system review

Tenant governance

Each institution receives controls derived from its context. Mandatory controls remain mandatory rather than optional extras.

Understand governance profiles

Evidence & Receipts

Inspect public system artifacts. Review findings, execution rights™, capabilities and actual execution remain distinguishable.

Open evidence

Investors & Private Equity

Examine the control position, institutional integration and technical review foundations before discussing funding.

Open investor review path

Press & media

The story, terminology, book materials and public evidence in one place, with a direct press contact.

Open press area

Announcements

Official company announcements and publications with dates and clearly stated status.

Read announcements
EVIDENCE AND RECEIPTS

Trace decisions. Inspect the evidence.

Evidence Library →

Receipts are the public evidence anchor of the site. They can document which input was processed, which rule state was active, which gate results were produced and how the result was cryptographically bound.

The limits matter just as much: cryptographic integrity is not automatically substantive legal correctness, truth of every external source or a guarantee of judicial acceptance. Those boundaries remain explicit.

Receipt workflow from input through rule and verdict to verify

Machine Law™ and immo.quick: clear answers

What is Machine Law™?

Machine Law™ is the conceptual framework for institutional control immediately before protected effect. Governing authority, rules, time conditions and dependencies must jointly support a specific action. The system does not create institutional authority.

Are Core™ and Serverless™ the same system?

No. immo.quick Core™ and immo.quick Serverless Edition™ are independent systems. Core™ binds institutional determinations to the context in which they arise. Serverless™ controls bound execution rights™ in integrated execution paths.

How does an execution right differ from an approval?

An approval records a decision at a particular time. An execution right must remain valid for the specific action under the governing current conditions. An earlier approval or an individual Gate PASS does not replace this check.

Where does ACES™ belong?

ACES™ is a closed domain within immo.quick Serverless Edition™. Gate 0 reviews the rule profile, not the person. ACES-A supports selection procedures and ACES-EN checks fitness evidence; adverse selection decisions remain with responsible people.

How does integration begin?

First define a specific protected action. Then identify authority sources, rules, dependencies and the actual execution path. The control boundary must be integrated where protected effect occurs; a general connection alone is insufficient.

In plain language

What is immo.quick?

immo.quick develops institutional trust infrastructure. Two independent systems connect institutional checks and protected actions to their governing conditions: immo.quick Core™ and immo.quick Serverless Edition™.

Publications and further developmentsBooks, background and announced extensions.

The new book by Rami Cherri

The Moment Before

Why institutions are losing control over their own actions in the age of AI, and how Machine Law™ gives it back

Friday, 4:47 p.m. A payment of 25 million euros leaves the bank: approved, checked, logged. Three minutes earlier, the decisive authority had been revoked. The book about the moment between decision and effect.

Hardcover 84,90 €Paperback 74,90 €E-book 49,99 €

Books

Two books, one line.

The Moment Before

The Moment Before

The book for a general readership. With a model case, real cases and a trailer. Hardcover, paperback and e-book.

The Moment Before →
Machine Law™

Machine Law™

The foundational work for institutions. Digital edition €19.90, print edition on request.

Machine Law™ →

The book about the moment before effect

The Moment Before · Rami Cherri

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 retailers

Corporate announcement · Planned Q1 2027

New announcement: immo.quick Capital

Developed in parallel since 2025: our independent investor platform adds capital access, matching and structured investment preparation to the business lifecycle. Rollout planned for the first quarter of 2027.

Read the Capital announcement →

Explore the architecture, sectors, book and QCORE

Compliance software, AI governance and institutional execution control raise different questions. This overview takes you directly to the relevant explanation and the available evidence.

immo.quick Core™

Independent architecture with hardware-backed assurance, TEEs and enclaves.

What does this mean for your next decision?

How does an execution right differ from a login?

A login identifies an authenticated user. An execution right binds a specific action to its authoritative prerequisites and current state. The Serverless Edition checks that right at the integrated execution boundary.

What can I examine in internal Live Due Diligence?

Controlled review access is intended for prospective customers, investors, buyers and auditors. It makes defined system states, system answers and their supporting evidence traceable. Available foundations and explicit limits remain part of the review.

How do Core and Serverless relate?

immo.quick Core and immo.quick Serverless Edition are independent systems. Core has its own hardware-backed trust architecture. The Serverless Edition controls execution rights in integrated applications and uses no TEEs or enclaves.

Why does institutional control matter for autonomous AI?

Autonomous systems can trigger specific actions while authority and conditions change. Institutional control therefore needs to connect current authority to the protected action. A prior approval status alone does not answer this question.

What does the Serverless Edition check immediately before execution?

At protected execution points that are actually integrated, the Serverless Edition checks whether a valid Execution Right bound to the specific action exists. The effect of the control depends on the integrated execution path and the available authoritative state data.

FOR INVESTORS, INSTITUTIONS, REGULATORS AND GOVERNMENTS

Assess the architecture for your institutional mandate.

The world is moving from software that supports decisions toward infrastructure that controls whether digital effects may occur at all. immo.quick addresses this institutional control boundary with two independent systems, sector-specific rule architecture and verifiable evidence.

The story behind immo.quick

How a personal experience led to institutional trust infrastructure and two books.

Founder & Origins →