Sectors, Provider Classes, Activities
What the institution actually is and does.
TECHNICAL REFERENCE · TENANT GOVERNANCE COMPILER
The tenant selects context. The architecture compiles requirements.
The compiler turns sectors, jurisdictions, activities, provider classes, risk attributes, deployment and assurance into a versioned Governance Profile. Multi sector contexts are merged monotonically. A stronger requirement cannot be downgraded by a weaker one.
FINAL_REQUIREMENT = STRONGEST_APPLICABLE_REQUIREMENT
Compiler Inputs
Jurisdictions, Applicability, Rule Versions
Which rules actually apply in the specific context.
Risk, Deployment, Criticality
Which additional controls become mandatory from risk and operating model.
Requirement Classes
SYSTEM_REQUIREDSECTOR_REQUIREDCONDITIONALLY_REQUIREDOPTIONALNOT_APPLICABLE
Monotonicity: NOT_APPLICABLE < OPTIONAL < CONDITIONALLY_REQUIRED < SECTOR_REQUIRED < SYSTEM_REQUIRED.
Endpoint Authority Integration
Endpoint Authority is provisioned through the same compiler. Telecommunications and Messaging make it sector required. Other sectors activate it only when activity, risk or effect requires the additional boundary. Existing sector closure remains intact.