Three-Tier Architecture

How the tiers interact:

This is a reference-host layout, not a universal loading contract. Verify which global/project instructions the chosen host loads, and retrieve the selected skills and documents on demand with their approved revisions. Tier 1 carries cross-project conventions, Tier 2 the project map, and Tier 3 procedural guidance; loading is not enforcement.

Conflicts can occur and follow the authority order in §4.5. For example: a cross-project rule can require a reviewed migration/recovery strategy; a selected project profile names its migration tool and runtime privileges; the task procedure verifies the actual forward path and applicable recovery contract. No tier can authorize an unsafe downgrade or override binding policy.

---