ATRIA

To establish the founding doctrine, Condition of Life, philosophical foundations, urban worldview, architectural principles and long-term institutional identity from which the complete ATRIA Corpus derives.

The original and autonomous doctrinal source of ATRIA. It precedes individual projects and provides the intellectual foundation for the Project Owner Edition, Master Project Book and detailed frameworks.

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

To provide the Project Owner with the client-facing doctrinal and identity reference for ATRIA.

Derived from the foundational archive and used with the specialized ATRIA frameworks applicable to one defined project.

Project Owner, investor representatives, board members, development leadership, operator leadership and appointed advisers.

To explain ATRIA as one complete project and direct the Project Owner’s appointed teams toward coherent implementation within an eligible existing urban building.

The integrated physical, spatial, architectural, operational and technical reference between the System Bible and the specialized frameworks.

Project Owner, MOD or Project Director, architects, interior designers, engineers, conservation specialists, operator, cost consultants and delivery teams.

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

Establishes 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 Document 03 to the protected relationships and governing condition of the system.

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

To define 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 define the ATRIA-specific control references used by project teams to verify coherence across territory, building, programme, design, operations and economics.

Translates institutional control into system-specific protected conditions.

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 validation subjects, references and findings against the corpus.

Project Owner, appointed professional teams, operator, financial advisers and 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.

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

To explain how the complete ATRIA corpus is used autonomously by the Project Owner and appointed teams to develop one defined project.

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

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

To define the urban territorial conditions required for ATRIA and the method for identifying, comparing and documenting cities and districts capable of preserving Presence.

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

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

To define the qualities an existing building and its immediate urban setting should present for coherent project application.

Translates territorial principles 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 preceding detailed design.

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

To translate architectural doctrine into concrete references for project application.

Provides practical architectural references subordinate to the Architecture Framework.

Architect, conservation specialist, masterplanner, engineers, operator technical teams and Project Owner.

To define 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 human conditions interiors must produce.

Establishes experiential, sensory, domestic and operational logic before detailed standards.

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

To translate interior doctrine into practical standards.

Provides detailed interior references for design and procurement teams.

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

To define the official typologies of the system and their complete capacity of use.

Consolidates spatial, occupancy, domestic, climatic and long-stay characteristics.

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 and protected operating conditions.

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

To explain how system doctrine produces a coherent economic logic.

Connects positioning, density, privacy, typology, service, territory and occupancy to reference economics.

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 modelling structure for project recalibration.

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

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

Provides project-specific financial application subordinate to Documents 15 and 16.

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

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

Connects doctrine and configuration to ownership, capital, partnership, operator and transfer structures.

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