Language:
DEEN
Language:
PRODUCTSâ–ľ
Home Core Serverless Edition Why It’s Different CDS — Constitutional Screening STFL — Sovereign Transaction Finance Layer Defence Verify Security All Gates
MOREâ–ľ
ASSURANCE
Authority Surface Execution Rights Capabilities Authoritative Sources Evidence Evidence Registry Fortress Baseline Adversarial Verification Machine Law Evolution
SOLUTIONS
Institutions Jurisdictions Due Diligence
RESOURCES
Facts Press Newsroom FAQ Machine Law — The Book Gate SDK Gamechangers The Sound of Machine Law
COMMERCIAL
Pricing Investors
Quantum Security 🔍 Search Request Access →
CANONICAL ARCHITECTURE BOUNDARY

Authority. Authorization. Evidence.

Three technical surfaces. One central rule: none may impersonate the other.

Current architecture →Claim Boundaries →
THE THREE SURFACES

Legitimacy comes from outside. Executability arises only after closure. Evidence comes after that.

This page is the concise canonical separation of the three layers. It does not replace a normative specification or case-specific legal assessment.

01 · AUTHORITY

Who may set the conditions?

Relevant authority remains outside the system. Law, regulation, courts, competent institutions or legitimate governance may set conditions within their actual competence.

BOUNDARYIdentity, infrastructure, consensus, AI or administrator status do not by themselves create normative authority.
02 · AUTHORIZATION

Does a complete right to the specific execution exist?

Gates provide domain determinations. The Execution Rights Graph closes Authority, Rule, Jurisdiction, Time and Dependency. Only complete closure can allow an Execution Right and a bound capability.

BOUNDARYGate PASS is not execution permission. The execution plane has no governance authority.
03 · EVIDENCE

What can be verified afterward?

The evidence layer cryptographically binds defined state, sequence, capabilities and execution relationships to the extent supported by the applicable evidence class.

BOUNDARYCryptography does not make false inputs true and does not decide substantive legal correctness or judicial admissibility.
AAUTHORITY
RRULE
JJURISDICTION
TTIME
DDEPENDENCY
CANONICAL CHAIN
01AUTHORITATIVE SOURCE
02NORMATIVE STATE
03DOMAIN DETERMINATION
04EXECUTION RIGHT
05BOUND CAPABILITY
06EXECUTION
07EVIDENCE
08VERIFY
CLAIM BOUNDARY

A technical proof must not become stronger than its artifact.

That is why immo.quick separates deterministic, cryptographically verifiable, statically enforced, provider-asserted and observational statements according to their actual evidentiary strength.

Claim Boundaries →Verify evidence →
AUTHORITY_SURFACE
authority_source: EXTERNAL
gate_pass_is_permission: false
execution_plane_governs: false
evidence_scope: BOUNDED
legal_correctness_from_crypto: false
Request Access →