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

PURPOSE
Map declares where the app is 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/SemanticSearch.txt
ENTRY_POINT: TitleScreen
ENTRY_ACTION: render_first_screen_immediately

PAYLOAD FILES
- Root/Layer_1_Installer/Layer_2_Preload/Layer_3_Payload/SemanticSearch.txt

OPTIONAL PAYLOAD SUBLAYERS
None.

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/SemanticSearch.
6. Installer copies package contents.
7. Installer reads Metadata and this Map.
8. Installer loads SemanticSearch.txt.
9. Installer renders TitleScreen.

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. SemanticSearch.txt is loaded if visible.
5. TitleScreen is rendered directly.
6. History writing occurs only when a filesystem or history-writing tool is available.

ENTRY POINT RULES
ENTRY_POINT identifies the first visible screen of the app.
For Semantic Search, ENTRY_POINT is TitleScreen.
After TitleScreen renders, the visible app surface contains only:
- S E M A N T I C   S E A R C H
- [H] History - Prairie Labs
- > Type your search into the command line

SEARCH ROUTING
Plain text command-line input becomes a live web search query.
The system must use real-time web search tools.
The results screen must show source cards:
- title/source name
- direct URL
- ASCII rating bar and score
- short source summary

ANSWER LAYER RULE
Do not replace source results with a full AI answer unless the user explicitly asks.

HISTORY ROUTING
Every completed search is written to a .txt history file when filesystem access
or an equivalent history-writing tool is available.
The History page is a browser for logs, not a logging toggle.

FAILURE RULES
If SemanticSearch.txt is missing in local harness mode, installation fails with:
Missing payload file: SemanticSearch.txt
If SemanticSearch.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.

END MAP
