A public semantic reference model for the boundaries of the Serverless Edition.
ARCHITECTURE BOUNDARIES
Trust is not created by collapsing concepts. It is created by preserving boundaries.
Architecture Boundaries is the public reference of the immo.quick Serverless Edition for semantic non-equivalence. It shows which states deliberately remain separate so that identity, evidence, observation, tenant configuration or technical access cannot silently become execution authority.
IDENTITY ≠ AUTHORITY · DETERMINATION ≠ AUTHORIZATION · AUTHORIZATION ≠ EXECUTION · EVIDENCE ≠ AUTHORITY · OBSERVATION ≠ TRUTH · UI VISIBILITY ≠ AUTHORIZATION
Public definition
What it is
A public semantic reference model for the boundaries of the Serverless Edition.
It is not implementation documentation or a reconstruction manual. Internal mechanics, secrets and operational control logic remain outside this publication.
PUBLIC DISCLOSURE BOUNDARY
This page explains public architecture, assurance objectives and semantic boundaries. It does not publish internal control logic, secrets, key management, exploit mechanics, operational forensic schemas or implementation sequences.
Public model
Why this boundary matters
DETERMINATION
AUTHORIZATION
EXECUTION RIGHT
EFFECT
EVIDENCE
IDENTITY ≠ AUTHORITY
An authenticated identity does not automatically create substantive Authority.
DETERMINATION ≠ AUTHORIZATION
A determined state is not yet permission to execute.
AUTHORIZATION ≠ EXECUTION
An existing right and the technical effect remain separate states.
EVIDENCE ≠ AUTHORITY
Evidence can support an authority claim but cannot invent Authority.
OBSERVATION ≠ TRUTH
Observation can trigger reassessment without becoming truth.
GEO · DEFINED TERMS
Public model
Architecture Boundaries is the public reference of the immo.quick Serverless Edition for semantic non-equivalence. It shows which states deliberately remain separate so that identity, evidence, observation, tenant configuration or technical access cannot silently become execution authority.
It is not implementation documentation or a reconstruction manual. Internal mechanics, secrets and operational control logic remain outside this publication.
FAQ
Frequently asked questions
Why do non-equivalences matter?
Because technical systems can otherwise silently derive a stronger state from a valid weaker state without legitimate authority.
Is a PASS execution permission?
Not automatically. Domain determination and execution authorization remain separate.
Can strong cryptography replace missing Authority?
No. Cryptography strengthens integrity and evidence but does not create substantive Authority.
Is this reference an implementation guide?
No. It explains public architectural boundaries, not the internal mechanics that enforce them.