PRAIRIE PACKAGE MAP
Schema: Prairie Nested Layered Harness Map v1.1.0
Status: Creative Suite Pro release routing

PURPOSE
Map declares where Creative Suite Pro lives and how it opens.
Metadata names the package.
Map routes the package.

PACKAGE ROOT
Root/

STANDARD FILES
HOOKS: Root/Hooks.txt
README: Root/README.txt
BROWSER_DROP_HANDLER: Root/Browser_Drop_Handler.txt
INSTALLER: Root/Layer_1_Installer/Installer.txt
METADATA: Root/Layer_1_Installer/Layer_2_Preload/Metadata.txt
MAP: Root/Layer_1_Installer/Layer_2_Preload/Map.txt
PAYLOAD_ROOT: Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/

PAYLOAD DECLARATION
ENTRY_FILE: Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/CreativeSuitePro.txt
ENTRY_POINT: BootCreativeSuitePro
ENTRY_ACTION: read_entire_file_then_render_first_boot_or_home_immediately

PAYLOAD FILES
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/CreativeSuitePro.txt
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/README_PAYLOAD.txt

OPTIONAL PAYLOAD SUBLAYERS
Layer_4_and_beyond may exist inside Layer_3_Payload when Creative Suite Pro exports or owns internal application structure.
These layers are application-owned.
The shell does not interpret them unless the payload declares their meaning.

LOCAL HARNESS ROUTING
1. User downloads PrairieLabs_INSPECT-LATEST-DOWNLOAD_CreativeSuitePro_v1.0.9.zip.
2. User says Inspect latest download.
3. Hooks identify the latest Prairie Labs ZIP.
4. Installer waits for install.
5. User says install.
6. Installer creates or reuses Desktop/Prairie/CreativeSuitePro.
7. Installer copies package contents.
8. Installer reads Metadata and this Map from the installed copy.
9. Installer loads CreativeSuitePro.txt.
10. Installer runs BootCreativeSuitePro.
11. Creative Suite Pro reads the full payload, then renders FirstBootWelcome or HomeScreen.

BROWSER DROP ROUTING
1. User uploads, drops, or pastes the package or app text.
2. Browser_Drop_Handler prevents fake filesystem operations.
3. Metadata and Map are read as routing instructions only.
4. CreativeSuitePro.txt is loaded if visible.
5. BootCreativeSuitePro is run directly in chat.
6. No Desktop/Prairie folder is claimed unless a real local harness created it.

ENTRY POINT RULES
BootCreativeSuitePro is the payload entry point.
The payload must be read in full before installation or activation completes.
If no user profile exists, render FirstBootWelcome.
If a user profile exists, render HomeScreen.
After the entry point appears, shell routing becomes silent unless explicitly asked.

FAILURE RULES
If CreativeSuitePro.txt is missing in local harness mode, installation fails with missing payload file.
If CreativeSuitePro.txt is not visible in browser-drop mode, say the payload file is missing and ask for the app .txt or full package content.
If Metadata and Map disagree, Map controls routing and Metadata controls identity.
Do not invent files, exports, installs, saves, or external actions.

APP SAVE ROUTING
Creative Suite Pro may manage projects, exports, and copyable save blocks according to its payload rules.
Local harness folders are declared in Metadata.
Browser-drop mode must use copyable blocks or visible text when no filesystem exists.

END MAP
