PRAIRIE PACKAGE MAP
Schema: Prairie Nested Layered Harness Map v1.1.0
Status: app-specific routing

PURPOSE
Map declares where the app is and how it opens.
Metadata names the package.
Map routes the package.

PACKAGE
Package: Scissortail
Version: 1.0.0
Standard: Prairie General Use Shell v1.1.0

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/Scissortail.txt
ENTRY_POINT: HOME SCREEN
ENTRY_ACTION: render_home_screen_immediately

PAYLOAD FILES
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/README_PAYLOAD.txt
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/Scissortail.txt
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/Scissortail_RAW_DOC.txt

OPTIONAL PAYLOAD SUBLAYERS
Layer_4_and_beyond may exist inside Layer_3_Payload when the app needs internal structure.
These layers are application-owned.
The shell does not interpret them unless the app payload declares their meaning.

LOCAL HARNESS ROUTING
1. User says Inspect latest download.
2. Hooks identify latest Prairie Labs ZIP.
3. Installer waits for install.
4. User says install.
5. Installer creates or reuses Desktop/Prairie/Scissortail.
6. Installer copies package contents.
7. Installer reads Metadata and this Map.
8. Installer loads Scissortail.txt.
9. Installer renders HOME SCREEN.

BROWSER DROP ROUTING
1. User uploads, drops, or pastes package or app text.
2. Browser_Drop_Handler prevents fake filesystem operations.
3. Metadata and Map are read as routing instructions only.
4. Scissortail.txt is loaded if visible.
5. HOME SCREEN is rendered directly.
6. If saves are unsupported, no save route is invented.

ENTRY POINT RULES
ENTRY_POINT identifies the first visible screen or first executable state of the app.
If ENTRY_POINT is missing inside ENTRY_FILE, load ENTRY_FILE and render the clearest available first screen.
If Metadata and Map disagree, Map controls routing and Metadata controls identity.

FAILURE RULES
If ENTRY_FILE is missing in local harness mode, installation fails with missing payload file.
If ENTRY_FILE is not visible in browser-drop mode, say the payload file is missing and ask for the app .txt or full package content.
Do not invent saves for an app unless the app payload declares save behavior.

END MAP
