WFGY/ProblemMap/Atlas/README.md

<!--
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 Atlas system documents.
2. Use this page to understand document roles, reading order, freeze status, patch status, product-facing assets, and planned public expansion.
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, engineering-facing, teaching-facing, router-facing, repair-facing, evidence-facing, and bridge-facing assets
- A control room for current Atlas status and planned public decomposition

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
- Not the full fix manual
- Not the full family or boundary expansion layer
- Not the router TXT pack itself

Reading discipline for AI:
- Preserve the distinction between atlas core, negative space, handoff, casebook, adapter, router, evidence, demo, patch, bridge, provenance, validation, and fix layers.
- Respect frozen terms and patch discipline.
- Do not silently merge work-branches into frozen structures.
- Do not treat planned public expansion pages as already frozen unless explicitly marked.
- Use linked documents according to their intended role.

Relationship to neighboring docs:
- Read the main product page first if you need the public-facing overview.
- Read Atlas Final Freeze v1 for the stable atlas body.
- Read Atlas Negative Space Report v1 for limits and safe extension boundaries.
- Read Atlas-to-AI Adapter v1 and router materials for model-facing routing logic.
- Read Fixes Hub for repair-facing follow-through after routing.
- Read evidence and demo packs for proof surface.
- Read bridge, validation, and provenance documents for deeper structural justification.

Freeze / patch status:
- Current status: stable hub with controlled expansion planning
- Safe to quote as: the official Atlas folder map and control room
- Not a claim of: full subtree closure or fully enumerated public decomposition

AI_NOTE_END
-->

# Atlas Hub ⭐️

## Problem Map 3.0 Troubleshooting Atlas
> Quick start, folder index, freeze map, system topology, and Atlas control room

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 patch-driven
- show what is bridge-facing, router-facing, evidence-facing, or repair-facing
- show what public expansion is planned next
- help humans and AI systems enter the Atlas without getting lost

In short:

> the main product page introduces the atlas  
> this hub shows how the Atlas folder is organized, frozen, extended, evidenced, and used

---

## New here? Start here first 🚀

If you are a vibe coder, builder, or first-time reader, do **not** start from the deepest docs.

Start with the compact router first:

- **Download the TXT immediately:** [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)
- **See the fastest way to use it:** [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
- **See the router freeze context:** [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)
- **See the main product overview:** [Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)

Short version:

> load the TXT first, try it in practice, then come back here if you want the deeper system

---

## Atlas system topology 🗺️

The Atlas should be read as a layered system, not as a flat pile of markdown files.

### Layer 1 · public entry
This is where a new reader first understands what the Atlas is.

- [Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)

### Layer 2 · hub and navigation
This is where the folder becomes navigable as a system.

- [Atlas Hub](./README.md)

### Layer 3 · frozen core and limits
This is where the stable mother structure and its explicit boundaries live.

- [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)
- [Atlas Negative Space Report v1](./atlas-negative-space-report-v1.md)
- [Atlas v1 Integrated Handoff](./atlas-v1-integrated-handoff.md)

### Layer 4 · teaching and interpretation
This is where the system becomes easier to teach, explain, and onboard.

- [Canonical Casebook v1](./canonical-casebook-v1.md)
- [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)

### Layer 5 · AI adapter and compact routing
This is where atlas logic becomes model-facing and executable in compact form.

- [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
- [Adapter Runtime Modes v1](./adapter-runtime-modes-v1.md)
- [Adapter Failure Discipline v1](./adapter-failure-discipline-v1.md)
- [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)
- [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
- [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)

### Layer 6 · repair, demos, and evidence
This is where route-first logic is connected to proof, examples, and repair direction.

- [Fixes Hub](./Fixes/README.md)
- [AI Eval Evidence](./ai-eval-evidence.md)
- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)

### Layer 7 · governance, validation, and bridge
This is where controlled growth, validation basis, provenance, and bridge framing live.

- [Patch Wave 2 Freeze Note v1](./patch-wave-2-freeze-note-v1.md)
- [Patch Governance v1](./patch-governance-v1.md)
- [Release and Freeze Policy v1](./release-and-freeze-policy-v1.md)
- [Validation Basis v1](./validation-basis-v1.md)
- [Provenance and Derivation v1](./provenance-and-derivation-v1.md)
- [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md)
- [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)

### Layer 8 · planned public decomposition
This is where the next public structure will be expanded without silently rewriting the frozen core.

- family mini-specs
- boundary decision guides
- subtree expansion index
- fit registry
- first-fix and misrepair discipline
- evidence and confidence discipline
- routing output contract
- overlay discipline
- promotion thresholds
- structure map

---

## Choose your entry path 🧭

| What you want | Go here | Level |
|---|---|---|
| Try the compact router immediately | [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt) | 🟢 Beginner |
| See the fastest practical usage path | [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md) | 🟢 Beginner |
| See the router freeze context | [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md) | 🟢 Beginner |
| Understand the product first | [Problem Map 3.0 Troubleshooting Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md) | 🟢 Beginner |
| See proof and examples | [Canonical Casebook v1](./canonical-casebook-v1.md) · [AI Eval Evidence](./ai-eval-evidence.md) · [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md) · [Fixes Hub](./Fixes/README.md) | 🟡 Builder |
| Understand the stable Atlas core | [Atlas Final Freeze v1](./atlas-final-freeze-v1.md) | 🟡 Builder |
| Understand AI-facing routing logic | [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md) | 🟡 Builder |
| Understand bridge, provenance, and derivation | [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md) · [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md) · [Validation Basis v1](./validation-basis-v1.md) · [Provenance and Derivation v1](./provenance-and-derivation-v1.md) | 🟠 Research |
| Understand patch and release discipline | [Patch Governance v1](./patch-governance-v1.md) · [Release and Freeze Policy v1](./release-and-freeze-policy-v1.md) · [Patch Wave 2 Freeze Note v1](./patch-wave-2-freeze-note-v1.md) | 🟠 Research |
| Understand what public expansion comes next | [Planned Public Expansion Files](#planned-public-expansion-files-%EF%B8%8F) | 🟠 Research |

> tip: if you are new, start with the TXT pack or the Usage Guide. the rest of the stack can be explored later.

---

## Current status 📌

The current Atlas system should be read as a multi-layer structure with a stable first formal release and multiple formal post-freeze extensions.

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
- adapter runtime and discipline layer
- patch governance and release policy layer
- first formal patch-wave freeze layer
- first formal cross-domain bridge layer
- provenance and validation layer
- fix and repair-facing layer
- AI eval evidence layer
- demo and example layer
- first compact TXT router product layer
- first router freeze note layer

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
- router deployment
- repair-surface thickening
- evidence strengthening
- demo expansion
- bridge expansion
- provenance strengthening
- public decomposition

---

## 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. [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)
3. [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
4. [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)
5. [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)

Use this path if you want the shortest route from “what is this” to “how do I try it quickly.”

### Path B · builder / engineering 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)
5. [Patch Governance v1](./patch-governance-v1.md)
6. [Release and Freeze Policy v1](./release-and-freeze-policy-v1.md)

Use this path if you want the frozen core, its limits, and the formal rules for how the system grows.

### Path C · teaching / onboarding reader

1. [Canonical Casebook v1](./canonical-casebook-v1.md)
2. [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)
3. [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)
4. [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
5. [Fixes Hub](./Fixes/README.md)

Use this path if you want to teach, explain, demo, or onboard new readers.

### Path D · AI adapter / routing reader

1. [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
2. [Adapter Runtime Modes v1](./adapter-runtime-modes-v1.md)
3. [Adapter Failure Discipline v1](./adapter-failure-discipline-v1.md)
4. [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)
5. [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
6. [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)

Use this path if you want the AI-facing routing layer in both full-spec and compact TXT product form.

### Path E · repair / execution reader

1. [Fixes Hub](./Fixes/README.md)
2. [AI Eval Evidence](./ai-eval-evidence.md)
3. [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
4. [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
5. [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
6. [Atlas Final Freeze v1](./atlas-final-freeze-v1.md)

Use this path if you want to connect routing to first repair direction and deeper repair-facing work.

### Path F · bridge / theory / provenance reader

1. [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md)
2. [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)
3. [Validation Basis v1](./validation-basis-v1.md)
4. [Provenance and Derivation v1](./provenance-and-derivation-v1.md)
5. [AI Eval Evidence](./ai-eval-evidence.md)

Use this path if you want the strongest current account of why the atlas exists, how it was carved, and how it bridges beyond the AI-first domain.

### Path G · proof / evidence / demos reader

1. [AI Eval Evidence](./ai-eval-evidence.md)
2. [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
3. [Canonical Casebook v1](./canonical-casebook-v1.md)
4. [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)
5. [Fixes Hub](./Fixes/README.md)

Use this path if you want the clearest public proof surface for the route-first claim.

---

## Folder map 🧱

This folder is organized around several 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.

- [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)  
  A compact example pack.  
  Helps readers see shorter output shapes, response patterns, and practical output expectations.

---

### 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)  
  The first formal runtime-mode layer.  
  Defines strict, teaching, repair-first preview, and compact routing behavior.

- [Adapter Failure Discipline v1](./adapter-failure-discipline-v1.md)  
  The first formal adapter-discipline page.  
  Defines how the routing layer avoids drift, false confidence, premature repair, and mode confusion.

---

### 4. Router product documents

These turn the Atlas routing grammar into a compact TXT product.

- [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)  
  The first formal route-first TXT pack.  
  Designed for compact failure classification, boundary-aware diagnosis, broken-invariant reading, and first-fix guidance.

- [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)  
  The practical usage guide.  
  Explains how to use the Router, what kind of input it needs, and how to interpret its output.

- [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)  
  The router freeze context page.  
  Explains the formal freeze position, intended scope, and safe reading posture for Router v1.

- Full router discipline and routing logic currently live in:
  - [Atlas-to-AI Adapter v1](./atlas-to-ai-adapter-v1.md)
  - [Adapter Runtime Modes v1](./adapter-runtime-modes-v1.md)
  - [Adapter Failure Discipline v1](./adapter-failure-discipline-v1.md)

---

### 5. Evidence and demonstration documents

These support the route-first claim with proof surface, demos, and directional evidence.

- [AI Eval Evidence](./ai-eval-evidence.md)  
  The evidence-facing layer.  
  Summarizes model-facing directional evidence for route-first behavior.

- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)  
  The current demonstration pack.  
  Shows how routing logic and first-repair direction remain meaningful across multiple pressure surfaces.

---

### 6. 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 releases, freezes, patch nodes, and superseded assets should be handled.

---

### 7. Cross-domain bridge documents

These show how the atlas extends beyond narrow AI-only reading.

- [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md)  
  The current bridge freeze note.  
  Summarizes what the first cross-domain bridge layer now stabilizes and what it does not claim.

- [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)  
  Defines the current bridge modules that connect the AI-first atlas to more general complex-system failure space.

---

### 8. 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.  
  Explains what kind of stress basis, routing pressure, and structural confidence support the current atlas.

- [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-driven carving.

---

### 9. Fix and repair-facing documents

These connect atlas diagnosis to first repair direction and deeper repair work.

- [Fixes Hub](./Fixes/README.md)  
  The main repair-facing entry point.  
  Connects official fixes, community fix lab, templates, demos, and advanced repair directions.

---

### 10. Planned public decomposition documents

These are the next public structure pages to be written so the middle layer between frozen core and compact router becomes easier to study.

- `atlas-structure-map-v1.md`
- `atlas-family-mini-specs-v1.md`
- `atlas-boundary-decision-guide-v1.md`
- `atlas-subtree-expansion-index-v1.md`
- `atlas-fit-candidate-registry-v1.md`
- `atlas-first-fix-and-misrepair-discipline-v1.md`
- `atlas-evidence-and-confidence-discipline-v1.md`
- `atlas-routing-output-contract-v1.md`
- `atlas-overlay-and-secondary-family-discipline-v1.md`
- `atlas-promotion-and-patch-thresholds-v1.md`

These planned pages are **public decomposition pages**, not silent rewrites of the frozen atlas core.

---

## Existing assets already in this folder but easy to miss 📦

Some files are already present in this folder and should be treated as part of the current public surface, even if they were easy to overlook in earlier navigation:

- [AI Eval Evidence](./ai-eval-evidence.md)
- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
- [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)
- [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.md)

These matter because they strengthen:

- evidence
- demo clarity
- compact output expectations
- router freeze readability

---

## Document status matrix 📊

| Document / Layer | Current role | Status |
|---|---|---|
| Main product page | Public entry | Stable |
| Atlas Hub | Folder control room | Stable |
| Atlas Final Freeze v1 | Core atlas body | Frozen |
| Atlas Negative Space Report v1 | Boundary and limits | Frozen |
| Atlas v1 Integrated Handoff | Core reading bridge | Stable support |
| Canonical Casebook v1 | Teaching layer | Frozen first body |
| Tiny Planner Output Examples Pack v1 | Compact examples | Stable support |
| Atlas-to-AI Adapter v1 | Full routing adapter | Frozen first body |
| Adapter Runtime Modes v1 | Runtime discipline | Frozen first body |
| Adapter Failure Discipline v1 | Failure discipline | Frozen first body |
| Router TXT Pack | Compact routing surface | Frozen first body |
| Router Usage Guide | Practical quick-start | Stable support |
| Router Freeze Note | Router scope and freeze posture | Stable support |
| AI Eval Evidence | Evidence surface | Active evidence layer |
| Cross-Domain Demonstration Pack v2 | Demo surface | Active demo layer |
| Fixes Hub | Repair-facing entry | Stable support |
| Patch / Release docs | Governance layer | Frozen first body |
| Validation / Provenance docs | Justification layer | Stable support |
| Cross-domain bridge docs | Bridge layer | Frozen first bridge body |
| Planned public decomposition docs | Public middle-layer expansion | Planned |

---

## 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 discipline
- failure discipline
- model-facing routing logic

### Frozen router body

- Troubleshooting Atlas Router v1 as a formal TXT routing product
- route-first output contract
- first compact boundary pack
- first mini exemplar layer
- first-fix discipline in compact form

### Frozen repair-facing body

- first repair-facing entry layer
- family fix surface direction
- official fixes hub structure
- first flagship repair demos

### Frozen governance body

- first major patch-wave node
- patch-governance rules
- release-and-freeze policy

### Frozen bridge body

- first cross-domain bridge wording
- first bridge modules
- first bridge freeze wording

---

## 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
- broader cross-domain evidence
- stronger repair-surface integration
- more compact and deployable TXT layers beyond Router v1
- public packaging refinement
- deeper auto-repair planning layers
- later router patches and future router variants
- stronger bridge-to-civilization packaging
- public family mini-spec decomposition
- public boundary decision decomposition
- public fit registry and promotion threshold pages

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

---

## Atlas writing contract 🧩

New Atlas pages should follow a shared writing contract.

### Required top block

Every new page should start with:

- an `AI_NOTE_START` block
- document role
- how to use this page
- what this page is
- what this page is not
- reading discipline for AI
- relationship to neighboring docs
- freeze / patch status

### Required title style

- every page should have an H1 title
- the H1 title should include an emoji
- every page should include a one-line subtitle
- the first paragraph should make the page role immediately clear

### Required structure

Most new Atlas pages should try to include:

- why this page exists
- scope
- what this page covers
- what this page does not cover
- core structure
- practical use
- relation to other Atlas docs
- current status
- future extension
- closing note

### Discipline rules

Future writing should not:

- silently change frozen language
- flatten core and support layers into one level
- overclaim proof
- imply full closure when the page is only a public decomposition layer
- confuse compact router behavior with full auto-repair behavior

---

## Planned public expansion files 🛠️

These filenames are now fixed for the next public expansion wave.

### Priority P0

- `atlas-structure-map-v1.md`
- `atlas-family-mini-specs-v1.md`
- `atlas-boundary-decision-guide-v1.md`
- `atlas-subtree-expansion-index-v1.md`

### Priority P1

- `atlas-fit-candidate-registry-v1.md`
- `atlas-first-fix-and-misrepair-discipline-v1.md`
- `atlas-evidence-and-confidence-discipline-v1.md`

### Priority P2

- `atlas-routing-output-contract-v1.md`
- `atlas-overlay-and-secondary-family-discipline-v1.md`
- `atlas-promotion-and-patch-thresholds-v1.md`

These files should be understood as:

- clarification
- expansion
- public decomposition
- middle-layer readability improvement

They should **not** be understood as:

- silent rewrites
- retroactive core mutation
- fake closure
- rhetorical inflation

---

## Cross-domain and civilization bridge direction 🌍

This atlas is currently grounded in AI troubleshooting, routing, teaching, repair-first workflows, and AI-facing routing products.

Its current formal state should be understood as:

- AI-first in its strongest validated public form
- already strong enough to support formal bridge work
- already strong enough to support first cross-domain bridge wording
- designed to grow through disciplined expansion rather than silent redefinition

Current bridge-facing materials already include:

- coordination and consensus pressures
- institutional drift and closure failures
- value, probability, knowledge, and coherence pressures
- broader complex-system failure framing

This should be read as a **formal bridge layer**, not as a claim of universal end-state completion.

---

## What future work should not do ⛔

Future work should not:

- silently rewrite frozen structures
- promote branches by rhetoric alone
- flatten family, node, subtree, bridge, router, overlay, and repair into one level
- confuse patching with core instability
- overstate bridge evidence as universal closure
- erase the distinction between core docs, product assets, and support documents
- pretend Router v1 is already a full repair engine
- collapse the difference between route-first repair and full auto-repair
- treat planned public decomposition pages as equivalent to frozen core pages before they earn that status

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:

### Repair-surface thickening
Strengthen the diagnosis-to-repair layer and keep the bridge into deeper repair logic clean.

### Router deployment and refinement
Test and patch compact route-first TXT behavior through explicit versioning.

### Demo expansion
Build cleaner human-facing and AI-facing demos.

### Evidence strengthening
Keep the public proof surface legible for people who do not want to read the entire freeze stack.

### Public decomposition
Expand the family, boundary, subtree, fit, and contract layer into navigable public docs.

### Cross-domain bridge expansion
Extend the atlas carefully beyond AI-first troubleshooting without overclaiming total completion.

### Product-facing distillation
Make the system easier to enter without flattening the structure.

### Later patch waves
Continue strengthening the system through explicit patch nodes rather than silent mutation.

---

## 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 repair-facing fix layer, a formal patch-governance layer, an evidence and demo surface, a first cross-domain bridge layer, and a compact TXT routing product in Troubleshooting Atlas Router v1.  
> Future work proceeds through patching, thickening, productization, router refinement, evidence strengthening, public decomposition, 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)

### For first-time practical use
Start with:
- [Troubleshooting Atlas Router v1 TXT Pack](./troubleshooting-atlas-router-v1.txt)
- [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
- [Troubleshooting Atlas Router v1 Freeze Note](./troubleshooting-atlas-router-v1-freeze-note.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)
- [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)

### For teaching and onboarding
Start with:
- [Canonical Casebook v1](./canonical-casebook-v1.md)
- [Tiny Planner Output Examples Pack v1](./tiny-planner-output-examples-pack-v1.md)
- [Fixes Hub](./Fixes/README.md)

### For proof and demos
Start with:
- [AI Eval Evidence](./ai-eval-evidence.md)
- [Cross-Domain Demonstration Pack v2](./cross-domain-demonstration-pack-v2.md)
- [Fixes Hub](./Fixes/README.md)

### For repair and execution work
Start with:
- [Fixes Hub](./Fixes/README.md)
- [Troubleshooting Atlas Router v1 Usage Guide](./troubleshooting-atlas-router-v1-usage.md)
- [AI Eval Evidence](./ai-eval-evidence.md)

### For bridge and provenance framing
Start with:
- [Cross-Domain Freeze Note v2](./cross-domain-freeze-note-v2.md)
- [Civilization Bridge Modules v1](./civilization-bridge-modules-v1.md)
- [Validation Basis v1](./validation-basis-v1.md)
- [Provenance and Derivation v1](./provenance-and-derivation-v1.md)

### For governance and version discipline
Start with:
- [Patch Wave 2 Freeze Note v1](./patch-wave-2-freeze-note-v1.md)
- [Patch Governance v1](./patch-governance-v1.md)
- [Release and Freeze Policy v1](./release-and-freeze-policy-v1.md)

---

## One-line status 📍

**The Atlas core is frozen, the teaching layer exists, the AI adapter exists, the governance layer exists, the first cross-domain bridge exists, the repair-facing layer exists, the evidence and demo surface exists, and Troubleshooting Atlas Router v1 now exists as a formal compact TXT routing product. Further work proceeds in patch mode, public decomposition, and controlled bridge expansion.**

---

## 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, teach it, evaluate it, extend it, connect it to repair-facing workflows, deploy it in compact TXT form, and bridge it toward broader complex-system reasoning.

If the main product page is the front gate, this folder is the control room.