UAI Memory Handoff Map

Last reviewed UTC: 2026-08-12T00:00:00Z Source status: approved Package version authority: E:/Source/WP/workspace.uai

Launch-baseline read order

1. AGENTS.md
2. .uai/readme.human
3. .uai/identity.uai
4. .uai/world-context.uai
5. .uai/totem.uai
6. .uai/taboo.uai
7. .uai/short-term-memory.uai
8. .uai/coding-standards.uai
9. .uai/system-profile.uai
10. .uai/receiver-brief.uai
11. .uai/startup-packet.uai
12. .uai/project-handoff.uai
13. .uai/file-handoff.uai
14. .uai/long-term-memory.uai
15. .uai/exports/manifest.json
16. .uai/exports/package-model.json
17. .uai/exports/file-deck.json
18. docs/index.md
19. docs/uai-memory-package-current-alignment.md
20. docs/long-term-memory-map.md

Export map

• .uai/exports/manifest.json is the active machine manifest.
• .uai/exports/package-model.json records the package profile, review gates, wizard boundary, and current setup posture.
• .uai/exports/file-deck.json records the receiver file deck.
• .uai/exports/llms.txt and .uai/exports/llms-full.txt summarize the current handoff for LLM readers.

Agent File Handoff rule

If human or AI intake files are dropped into agent-file-handoff/Content/, agent-file-handoff/Improvement/, or the package root, the next receiver must review each file, apply or reject it, record the disposition, and move processed source to Archive/ unless Mike explicitly keeps it active.

Safety gate

Do not promote generated anchors, raw report-derived claims, or archive-only intake notes without explicit review.