What does immo.quick do?

immo.quick deterministically resolves whether the defined authority, rule, jurisdiction, time and dependency conditions close into a valid Execution Right for a governed action, and preserves claim-bounded evidence of that technical process.

Does a Gate PASS in immo.quick mean an action is permitted to execute?

No. A Gate PASS is not execution permission. Gates perform domain determination only. The Execution Rights Graph separately resolves whether Authority, Rule, Jurisdiction, Time and Dependency close into a valid right to execute.

How many jurisdictions does immo.quick cover?

immo.quick's Gate Catalog covers 53 jurisdictions, spanning regulatory, institutional, sector-specific and infrastructure-level domains, with an authorization result typically returned in under 800ms at the 95th percentile.

What happens if one required execution condition is absent?

If a required Authority, Rule, Jurisdiction, Time or Dependency condition is absent, no valid capability exists in the governed execution path for that action. A prior PASS does not manufacture continuing permission.

What is immo.quick's current security assurance state?

Fortress Baseline 1.2.0 is sealed, normative provenance is active, adversarial verification stands at 90 of 90 defined test cases passed, and the authoritative source landscape is live and independently inspectable.

Institutional Trust Infrastructure | Execution Rights

EXECUTION REQUIRES A RIGHT.

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.

NO VALID EXECUTION RIGHT · NO CAPABILITY · NO EXECUTION

Not everything a system knows may become execution.

AI, data, policies, scores, humans and gates may determine or analyse state. None of them independently creates execution authority.

BEFORE THE LINE

AI / LLMPOLICYDATAHUMAN INPUTSCOREGATE DETERMINATION

Determination may inform the state. It does not create permission.

EXECUTION BOUNDARY

AFTER CLOSURE

VALID EXECUTION RIGHT↓BOUND CAPABILITY↓EXECUTION↓EVIDENCE

AAUTHORITY

RRULE

JJURISDICTION

TTIME

DDEPENDENCY

5/5 CLOSEDEXECUTION RIGHT MAY EXIST4/5 CLOSED → NO VALID EXECUTION RIGHT

Official law text. Real screening. Publicly visible collision record.

The original text from Federal Law Gazette I 2026 No. 107 was screened in full against Gate 0. The result is not a blog paragraph, but a directly linked evidence artifact with exact source, input length, deterministic screening and traceable collision fields.

SOURCEBGBl. I 2026 Nr. 107

INPUT68,793 characters

RESULTHARD_BLOCK · 3

CLAIM CLASSForensic screening

01 · SOURCE OF LEGITIMACY

Authority

Law, regulation, courts, competent institutions or legitimate governance define the relevant conditions. The system itself is not the source.

CANBind authoritative conditions and their applicable state.

CANNOTBe newly created by AI, score, admin privilege or infrastructure.

02 · EXECUTION EFFECT

Authorization

Domain Determination supplies state. The Execution Rights Graph resolves across Authority, Rule, Jurisdiction, Time and Dependency whether a complete right to the specific execution can exist.

CANResolve a valid Execution Right and from it a bound capability.

CANNOTCompensate for missing authority with positive scores or other gates.

03 · VERIFIABLE RECORD

Evidence

Receipts, state binding, sequence and cryptographic integrity make the technical chain inspectable. Evidence remains bounded to what its artifact actually supports.

CANEstablish integrity, binding, sequence and the defined execution relationship.

CANNOTGuarantee substantive legal correctness, judicial admissibility or complete external reality.

The old model observes. Machine Law governs execution rights.

Highly regulated systems need more than scores, alerts and post-hoc logs. They need an inspectable separation between determination, external authority, Execution-Rights Closure, capability and evidence. A decision alone must never manufacture the right to execute it.

OLD MODEL

Observe execution

Score. Alert. Escalate. Log. Explain after the action has already happened.

MACHINE LAW

Govern execution rights

Authority → Rule State → Jurisdiction → Time → Dependencies → Determination → Execution-Rights Closure → Capability → Evidence.

A Gate Judgment is not an Execution Right. The machine does not create sovereign authority. It binds to an external authority state and makes the resulting execution path inspectable.

What the architecture never confuses.

AUTHORITY

Comes from legitimate external sources.

The system does not create authority.

GATE

Produces a domain determination.

PASS is not execution permission.

CAPABILITY

Follows a complete authorization state.

It does not substitute for an Execution Right.

EVIDENCE

Establishes supported integrity and binding properties.

It does not decide substantive legal correctness.

Authentication ≠ Authority. The endpoint needs its own right to create effect.

16 Endpoint Authority invariants, 12 Messaging invariants, 56 execution surfaces and 41 live executed tests. Telecommunications providers, consumer messengers and social communications platforms receive a dedicated sector governance composition with provider classification, Lawful Access Authority and point of effect revalidation.

EXECUTION REQUIRES A RIGHT.

Responsible disclosure becomes provable.

Institutional Trust Infrastructure for execution rights.

PASS is not permission.

Do not trust the claim. Inspect the architecture and evidence.

Regulation is moving toward execution.

A gate does not issue an order. A PASS does not create a right.

Closure is binary. Not approximate.

Not everything a system knows may become execution.

Official law text. Real screening. Publicly visible collision record.

Machine Law → two independent architectures.

Hardware-backed environmental assurance.

Provider-neutral execution authorization.

Three surfaces. None may impersonate the other.

Authority

Authorization

Evidence

Every system leaves logs. Very few leave evidence.

Don't reconstruct history. Seal it.

Four properties. No leap of faith.

Four domains. No vertical stands alone.

Not only the architecture is inspectable. The claim itself has a boundary.

Your next audit has already started.

The old model observes. Machine Law governs execution rights.

Observe execution

Govern execution rights

Five perspectives. One fundamental question.

Stop managing compliance after execution.

Do not only inspect reports. Inspect the control architecture itself.

Surface collisions before consequences appear.

Look beneath Compliance SaaS.

What sits underneath regulated software?

We do not ask institutions to believe the architecture.

What the architecture never confuses.

Test laws while they are still drafts.

Observation. Prediction. Intervention. Authorization.

The boundaries that turn control into institutional infrastructure.

THE MODEL MAY THINK. AUTHORITY STAYS OUTSIDE THE MODEL.

Authentication ≠ Authority. The endpoint needs its own right to create effect.

One infrastructure. Multiple sectors. No generic tenant.