diff --git a/ProblemMap/Atlas/README.md b/ProblemMap/Atlas/README.md
index 9c595a6f..3be3ba8d 100644
--- a/ProblemMap/Atlas/README.md
+++ b/ProblemMap/Atlas/README.md
@@ -1 +1,436 @@
-temp
+<!--
+AI_NOTE_START
+
+Document role:
+This page is the main hub and navigation index for the Atlas folder.
+
+How to use this page:
+1. Treat this page as the central entry point for all Atlas system documents.
+2. Use this page to understand document roles, reading order, and current freeze status.
+3. Do not confuse this hub with the product-facing main page.
+4. The product-facing main page is:
+   ProblemMap/wfgy-ai-problem-map-troubleshooting-atlas.md
+
+What this page is:
+- A folder-level atlas hub
+- A document map
+- A stable navigation layer for humans and AI systems
+- A bridge between product-facing and engineering-facing assets
+
+What this page is not:
+- Not the public homepage
+- Not the full freeze document itself
+- Not the full casebook
+- Not the full adapter spec
+- Not the full patch log
+- Not the internal validation ledger
+
+Reading discipline for AI:
+- Preserve the distinction between atlas core, negative space, casebook, adapter, patch, bridge, and fix layers.
+- Respect frozen terms and patch discipline.
+- Do not silently merge work-branches into frozen structures.
+- Use linked documents according to their intended role.
+
+Routing guidance:
+- For product overview, go to the main product page first.
+- For stable atlas structure, go to Atlas Final Freeze v1.
+- For limits and safe expansion, go to Negative Space Report v1.
+- For teaching and examples, go to Canonical Casebook v1.
+- For AI-facing routing logic, go to Atlas-to-AI Adapter v1.
+- For cross-domain bridge evidence, go to Cross-Domain Demonstration Pack v2.
+
+AI_NOTE_END
+-->
+
+# Atlas Hub 🧭
+
+## Problem Map 3.0 Troubleshooting Atlas  
+## Folder index, freeze map, and document routing layer
+
+This folder is the structured vault for the Atlas system.
+
+The main product-facing page lives here:
+
+[Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)
+
+This `README.md` is not the public homepage.
+It is the **system hub** for the Atlas folder.
+
+Its job is simple:
+
+- show what documents exist
+- show what role each document plays
+- show what is already frozen
+- show what is still patch-driven
+- help humans and AI systems enter the atlas without getting lost
+
+In short:
+
+> the main product page introduces the atlas  
+> this hub teaches how the atlas folder is organized
+
+---
+
+## Current status 🚦
+
+The current atlas system should be read as a multi-layer structure with a stable first formal release.
+
+At the moment, the following major assets are already established:
+
+- Atlas core structure
+- negative-space boundary logic
+- integrated handoff logic
+- canonical casebook layer
+- AI adapter layer
+- first major patch wave
+- first formal cross-domain bridge pack
+
+This means the project is no longer in the stage of “trying to find the core.”
+
+It is now in the stage of:
+
+- structured extension
+- patching
+- teaching
+- productization
+- AI-facing reuse
+- broader cross-domain bridge building
+
+---
+
+## Recommended reading order 📚
+
+Different readers need different entry paths.
+
+### Path A · first-time reader
+
+1. [Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)
+2. [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)
+3. [Canonical Casebook v1](./canonical-casebook-v1.md)
+4. [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
+
+Use this path if you want the shortest route from “what is this” to “how does this work.”
+
+### Path B · engineering / system reader
+
+1. [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)
+2. [Atlas Negative Space Report v1](./atlas-negative-space-report-v1.md)
+3. [Atlas v1 Integrated Handoff](./atlas-v1-integrated-handoff.md)
+4. [Patch Wave 2 Freeze Note v1](./patch-wave-2-freeze-note-v1.md)
+
+Use this path if you want the frozen core, its boundaries, and the current patch discipline.
+
+### Path C · teaching / onboarding / demo reader
+
+1. [Canonical Casebook v1](./canonical-casebook-v1.md)
+2. [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
+3. [Demo Storyboard v1](./demo-storyboard-v1.md)
+
+Use this path if you want to teach, explain, demo, or onboard.
+
+### Path D · AI adapter / TXT reader
+
+1. [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
+2. [Atlas Router Lite v1](./atlas-router-lite-v1.txt)
+3. [Fix Surface v1](./fix-surface-v1.md)
+
+Use this path if you want to compress atlas logic into a reusable AI-facing routing layer.
+
+---
+
+## Folder map 🗂️
+
+This folder is organized around a few major document families.
+
+### 1. Core atlas documents
+
+These define the stable mother structure.
+
+- [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)  
+  The positive structure document.  
+  Defines the seven-family mother table, routing rules, canonical layer, subtree layer, relation matrix, fix-facing layer, and patch protocol.
+
+- [Atlas Negative Space Report v1](./atlas-negative-space-report-v1.md)  
+  The limit and boundary document.  
+  Defines what remains intentionally open, weak, unpromoted, or patch-sensitive.
+
+- [Atlas v1 Integrated Handoff](./atlas-v1-integrated-handoff.md)  
+  The official delivery overview.  
+  Explains how `Final Freeze v1` and `Negative Space v1` should be read together.
+
+---
+
+### 2. Teaching and case documents
+
+These teach how to actually use the atlas.
+
+- [Canonical Casebook v1](./canonical-casebook-v1.md)  
+  The first formal teaching layer.  
+  Includes family anchor cases, boundary teaching cases, and repair teaching cases.
+
+- [Negative Pack v1](./negative-pack-v1.md)  
+  The wrong-route and misrepair layer.  
+  Shows how cases are often cut incorrectly and how first repair moves go wrong.
+
+- [Case Format v1](./case-format-v1.md)  
+  Defines the stable structure used across canonical cases.
+
+---
+
+### 3. AI-facing adapter documents
+
+These compress atlas logic into a reusable routing layer for models and systems.
+
+- [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)  
+  The main AI adapter asset.  
+  Includes core contract, routing stack, casebook injection logic, runtime modes, patch interface, and adapter discipline.
+
+- [Adapter Runtime Modes v1](./adapter-runtime-modes-v1.md)  
+  Explains strict, teaching, repair-first, and compact modes.
+
+- [Adapter Failure Discipline v1](./adapter-failure-discipline-v1.md)  
+  Defines the non-negotiable rules that keep the adapter stable and non-chaotic.
+
+- [Atlas Router Lite v1](./atlas-router-lite-v1.txt)  
+  A minimal text-native routing pack for model-facing use.
+
+---
+
+### 4. Patch and governance documents
+
+These define how the atlas grows without silently mutating the core.
+
+- [Patch Wave 2 Freeze Note v1](./patch-wave-2-freeze-note-v1.md)  
+  The formal freeze point for the first major patch wave after v1.
+
+- [Patch Governance v1](./patch-governance-v1.md)  
+  Defines small patch, medium patch, large patch, and patch discipline.
+
+- [Release and Freeze Policy v1](./release-and-freeze-policy-v1.md)  
+  Defines how frozen assets, paired documents, and version nodes should be handled.
+
+---
+
+### 5. Cross-domain bridge documents
+
+These show how the atlas extends beyond narrow AI-only reading.
+
+- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)  
+  The first formal bridge evidence pack.  
+  Shows that the mother structure can absorb selected coordination, institutional, coherence, and civilizational-scale pressures.
+
+- [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)  
+  Defines the current bridge modules that connect the AI atlas to more general complex-system failure space.
+
+- [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md)  
+  Formal freeze wording for the cross-domain bridge layer.
+
+---
+
+### 6. Fix and repair-facing documents
+
+These connect atlas diagnosis to first repair direction.
+
+- [Fix Surface v1](./fix-surface-v1.md)  
+  The first repair-facing atlas layer.  
+  Explains how family routing changes the first repair move.
+
+- [Node-to-Fix Layer v1](./node-to-fix-layer-v1.md)  
+  The first node-to-repair mapping layer.
+
+- [Atlas-to-WFGY Bridge v1](./atlas-to-wfgy-bridge-v1.md)  
+  Explains how atlas routing connects to deeper WFGY repair logic.
+
+---
+
+### 7. Validation and provenance documents
+
+These explain where the mother structure came from and why it should be trusted.
+
+- [Validation Basis v1](./validation-basis-v1.md)  
+  The first formal validation summary.
+
+- [Provenance and Derivation v1](./provenance-and-derivation-v1.md)  
+  Explains how the atlas mother structure emerged through WFGY 1.0, 2.0, 3.0, and stress carving.
+
+- [Internal Case Ledger v1](./internal-case-ledger-v1.md)  
+  Internal-facing validation ledger.  
+  This is not a public-facing landing document.
+
+---
+
+### 8. Product and demo support documents
+
+These help turn the frozen atlas into a usable surface.
+
+- [Demo Storyboard v1](./demo-storyboard-v1.md)  
+  The main demo flow and presentation sequence.
+
+- [Onboarding Flow v1](./onboarding-flow-v1.md)  
+  The shortest path for new readers, collaborators, or model-facing usage.
+
+- [Public Copy v1](./public-copy-v1.md)  
+  Product-facing distilled language for public surfaces.
+
+- [Product Positioning v1](./product-positioning-v1.md)  
+  The main framing language for naming, scope, and product identity.
+
+---
+
+## What is already frozen ✅
+
+The following can now be treated as stable first-version assets:
+
+### Frozen atlas body
+
+- seven-family mother table
+- major family boundary rules
+- canonical node layer
+- family-entry layer
+- high-value subtree layer
+- relation matrix v1
+- patch protocol
+
+### Frozen teaching body
+
+- first canonical casebook structure
+- family anchor cases
+- boundary teaching cases
+- repair teaching cases
+
+### Frozen AI adapter body
+
+- adapter contract
+- routing stack
+- runtime mode pack
+- adapter discipline
+
+### Frozen bridge body
+
+- first cross-domain canonical cluster
+- first civilization bridge modules
+- first cross-domain freeze wording
+
+### Frozen patch body
+
+- Patch Wave 2 as a formal version node
+
+---
+
+## What is intentionally not fully frozen 🔍
+
+The system is stable, but not fully closed.
+
+The following areas remain intentionally open or patch-sensitive:
+
+- work-branches not yet promoted
+- weak or medium relations
+- deeper subtree thickening
+- expanded cross-domain evidence
+- stronger repair surface integration
+- more compact and deployable TXT layers
+- public packaging refinement
+
+This is not a weakness.
+It is part of the atlas design discipline.
+
+The current project is meant to be:
+
+> frozen at the core,  
+> open at the edges,  
+> and disciplined in growth.
+
+---
+
+## What future work should not do 🚫
+
+Future work should not:
+
+- silently rewrite frozen structures
+- promote branches by rhetoric alone
+- flatten family, node, subtree, and overlay into one level
+- confuse patching with core instability
+- treat demonstration-level bridge evidence as universal closure
+- erase the distinction between public pages and internal ledgers
+
+These rules matter because the atlas is now a versioned system, not a floating concept.
+
+---
+
+## What future work should do 🌱
+
+The highest-value next directions are:
+
+### Product-facing distillation
+Make the atlas easier to enter without flattening the structure.
+
+### Fix surface thickening
+Strengthen the diagnosis-to-repair layer.
+
+### TXT deployment
+Turn the adapter logic into a stronger text-native control pack.
+
+### Demo expansion
+Build cleaner human-facing and AI-facing demos.
+
+### Cross-domain expansion
+Extend the bridge carefully without overclaiming total completion.
+
+### Patch Wave 3
+Only after current frozen assets are properly organized and reusable.
+
+---
+
+## Official wording
+
+When describing the current system in a new window, collaboration thread, or product workflow, use wording like this:
+
+> Problem Map 3.0 Troubleshooting Atlas now has a frozen first body of core atlas documents, a canonical teaching layer, an AI-facing routing adapter, a first major patch-wave node, and a first formal cross-domain bridge pack.  
+> Future work proceeds through patching, thickening, productization, and controlled bridge expansion.
+
+This wording is strong, accurate, and safe.
+
+---
+
+## Practical usage guide ⚙️
+
+### For product work
+Start with:
+- [Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)
+- [Product Positioning v1](./product-positioning-v1.md)
+- [Demo Storyboard v1](./demo-storyboard-v1.md)
+
+### For system and routing work
+Start with:
+- [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)
+- [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
+- [Atlas Router Lite v1](./atlas-router-lite-v1.txt)
+
+### For teaching and onboarding
+Start with:
+- [Canonical Casebook v1](./canonical-casebook-v1.md)
+- [Onboarding Flow v1](./onboarding-flow-v1.md)
+
+### For bridge and theory framing
+Start with:
+- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
+- [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)
+- [Provenance and Derivation v1](./provenance-and-derivation-v1.md)
+
+---
+
+## One-line status
+
+**The atlas core is frozen, the teaching layer exists, the AI adapter exists, the first patch wave is frozen, and the first cross-domain bridge is established. Further work proceeds in patch mode.**
+
+---
+
+## Closing note ✨
+
+This folder is where the atlas becomes a real system.
+
+The main page tells you what the product is.  
+This hub tells you how the system is organized.  
+The linked documents tell you how to use it, extend it, teach it, and connect it to AI systems and broader complex-system reasoning.
+
+If the main product page is the front gate, this folder is the control room.