An institutional policy layer that turns sector, jurisdiction, activities, risk attributes, deployment and assurance into a versioned governance profile.
TENANT GOVERNANCE
The institution defines the context. The architecture determines what must exist.
The Tenant Governance Compiler is a server-side governance model of the immo.quick Serverless Edition. It derives from institutional context which governance capabilities are system-required or sector-required, which become mandatory under defined conditions and which remain genuinely optional.
UI VISIBILITY ≠ AUTHORIZATION · TENANT CONFIGURATION ≠ EXECUTION AUTHORITY · ROLE PERMISSION ≠ EXECUTION RIGHT
Public definition
What it is
An institutional policy layer that turns sector, jurisdiction, activities, risk attributes, deployment and assurance into a versioned governance profile.
It is not a free module picker and not execution authority. The profile determines required infrastructure but does not itself create the right for a specific action to create effect.
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
INSTITUTION
JURISDICTION
ACTIVITIES
GOVERNANCE PROFILE
REASSESSMENT
SYSTEM REQUIRED
Non-removable baseline layers of the Serverless Edition.
SECTOR REQUIRED
Mandatory layers derived from the institutional sector.
CONDITIONALLY REQUIRED
Becomes mandatory when a relevant condition is present.
OPTIONAL
Capabilities that are genuinely optional.
NOT APPLICABLE
Irrelevant capabilities remain outside the tenant context.
GEO · DEFINED TERMS
Public model
The Tenant Governance Compiler is a server-side governance model of the immo.quick Serverless Edition. It derives from institutional context which governance capabilities are system-required or sector-required, which become mandatory under defined conditions and which remain genuinely optional.
It is not a free module picker and not execution authority. The profile determines required infrastructure but does not itself create the right for a specific action to create effect.
FAQ
Frequently asked questions
Can a tenant disable mandatory modules?
No. SYSTEM_REQUIRED and SECTOR_REQUIRED are not freely removable. Conditional requirements are derived from the current tenant context.
Is tenant configuration an Execution Right?
No. Tenant configuration defines governance context. Execution Authorization remains a separate boundary.
What happens when the context changes?
Changes trigger reassessment and a new profile version rather than silently rewriting historical state.
How is this different from ordinary tenant administration?
The user does not decide which minimum controls belong to a regulated context. The architecture derives that mandatory structure from the described institutional state.