KAAZA

To establish the founding doctrine, continental reading, governing Condition of Life, philosophical foundations, experiential principles, territorial logic and long-term institutional identity from which the complete KAAZA Corpus derives.

The Founding Bible is the original doctrinal source of KAAZA. It precedes project application and provides the intellectual and institutional foundation from which the Project Owner Edition, Master Project Book and detailed frameworks are derived.

Founder and system steward, Project Owner, principal investment decision-makers, senior operator leadership and selected institutional and professional advisers.

To define what KAAZA is, why it exists, the condition it protects and the principles of coherence the Project Owner must understand and preserve.

The primary doctrinal reference for the Project Owner. It establishes the system before project implementation begins.

Project Owner, investment leadership, senior advisers, operator leadership and appointed project directors.

To translate the KAAZA doctrine into a complete implementation structure for the Project Owner’s appointed teams.

The principal implementation manual connecting the System Bible to the detailed frameworks, guidelines and project-specific professional work.

Project Owner, architects, designers, engineers, operator, consultants, procurement and construction leadership.

To define the institutional governance embedded within a Governed Hospitality System without governing or administering the project.

Establishes the common institutional understanding of governance as a property of the corpus rather than a permanent external service.

Project Owner, legal and institutional advisers, appointed professional teams and operator leadership.

To translate the common institutional governance architecture into the particular doctrine of the system.

Connects the common governance principles of Document 03 to the protected relationships and governing condition of the system.

Project Owner, system interpreters, architects, designers, operators and appointed advisers.

To define the meaning of institutional control without creating project-management, construction or operational control.

Establishes the corpus as the permanent reference against which coherence and material departure are understood.

Project Owner, governance advisers, appointed teams, operator leadership and decision-makers.

To identify the particular conditions that allow the system to remain coherent and recognizable.

Translates institutional control into the system-specific conditions protected across territory, site, design, operations, economics and positioning.

Project Owner, appointed design and technical teams, operator and financial advisers.

To define what must be verified to determine whether a proposal, decision or configuration remains coherent with the system.

Establishes the subjects, references and possible findings of institutional validation against the corpus.

Project Owner, appointed professional teams, operator, financial advisers and internal project reviewers.

To provide the intellectual and documentary method used to assess a proposal against the corpus.

Supplies the common assessment sequence supporting compatibility conclusions without replacing professional or Project Owner authority.

Assessment team, Project Owner, appointed advisers and professional disciplines submitting evidence.

To explain how the system is applied to a project without organizing the work of the Project Manager or project teams.

Connects the complete corpus to project-specific interpretation from territorial application through opening and long-term operation.

Project Owner, development leadership, architects, designers, engineers, operator and financial teams.

To define the territories in which the system can ideally preserve its doctrine, positioning and value.

Establishes the territorial conditions that precede site selection, design and project configuration.

Project Owner, territorial advisers, planners, development teams, environmental and market advisers.

To define the qualities a site should present to permit a coherent application of the system.

Translates the territorial principles of Document 06 into physical, climatic, infrastructural, operational and economic site conditions.

Project Owner, development adviser, architect, planner, environmental, technical and financial teams.

To define the architectural doctrine of the system.

Establishes the architectural relationships that precede detailed design decisions and guide the Architecture Guidelines.

Project Owner, lead architect, planning, landscape, environmental and engineering teams.

To translate the architectural doctrine into concrete references for project application.

Provides practical architectural references while remaining subordinate to the Architecture Framework and project-specific professional responsibility.

Architect, masterplanner, landscape architect, engineers, operator technical teams and Project Owner.

To define the areas, categories, functional minimums and dimensional targets of the official typologies.

Provides the dimensional reference annex used with Documents 11, 12, 13 and 14.

Architect, interior designer, cost consultant, operator, technical teams and Project Owner.

To define the interior doctrine and the human conditions interiors must produce.

Establishes the protected interior relationships, material intelligence, atmospheric conditions and project outputs preceding the Interior Guidelines.

Project Owner, interior designer, architect, lighting and acoustic advisers, operator and procurement teams.

To translate the interior doctrine into practical standards.

Provides the detailed interior references used by the appointed design and procurement teams.

Interior designer, architect, lighting and acoustic advisers, FF&E, procurement, operator and Project Owner.

To define the seven official territorial typologies of KAAZA, their programme logic and their hospitality and residential boundaries.

Consolidates the territorial condition, programme logic, key ranges, residential eligibility and departure triggers of each official typology.

Project Owner, architect, interior designer, operator, cost consultant and financial teams.

To define how an operator may operate the system without redefining it.

Establishes the relationship between operator capability, operator identity and the protected operating conditions of the system.

Project Owner, operator-selection advisers, operator leadership, asset management and project teams.

To explain how the doctrine of the system produces a coherent economic logic.

Connects positioning, density, privacy, typology, service, territory and occupancy to the system's reference economic structure.

Project Owner, investment, development, market, operator and financial advisers.

To define the financial methodology applicable to projects of the system.

Translates the Economic Framework into a disciplined modelling structure that can be recalibrated for individual projects.

Project Owner, financial adviser, development manager, cost consultant, operator and lenders' advisers.

To apply the methodology of Document 16 to the actual data of a specific project.

Provides the project-specific financial application while remaining subordinate to the system's Economic Framework and Financial Models.

Project Owner, financial adviser, development manager, cost consultant, operator, financing parties and tax advisers.

To define the institutional and economic forms in which a project of the system may be developed.

Connects system doctrine and project configuration to ownership, capital, partnership, operator and long-term transfer structures.

Project Owner, development and investment advisers, legal counsel, operator, capital partners and asset-management teams.