mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-28 11:40:07 +00:00
299 lines
8.1 KiB
Markdown
299 lines
8.1 KiB
Markdown
<!--
|
|
AI_NOTE_START
|
|
|
|
Document role:
|
|
This page is the beginner-friendly quickstart guide for WFGY 4.0 Twin Atlas Engine.
|
|
|
|
What this page is for:
|
|
1. Help new readers understand where to start.
|
|
2. Show the fastest reading paths for different goals.
|
|
3. Prevent readers from getting lost inside the full WFGY 4.0 document family.
|
|
4. Turn the Twin Atlas release surface into something approachable for first-time users.
|
|
|
|
What this page is not:
|
|
1. It is not the flagship landing page.
|
|
2. It is not the full runtime constitution.
|
|
3. It is not the evidence summary page.
|
|
4. It is not the full protocol page.
|
|
5. It is not a benchmark claim page.
|
|
|
|
Reading order:
|
|
1. Read the Twin Atlas README first.
|
|
2. Use this page next if you are not sure where to go.
|
|
3. Pick the path that matches what you want:
|
|
- practical diagnosis
|
|
- governance
|
|
- runtime structure
|
|
- evidence and demos
|
|
|
|
Important boundary:
|
|
This page is a guided entry surface.
|
|
It is designed to reduce confusion and lower the first-reading burden.
|
|
It does not replace the deeper pages of WFGY 4.0.
|
|
|
|
AI_NOTE_END
|
|
-->
|
|
|
|
# 🚀 Quickstart
|
|
|
|
> New here? Start small, move clearly, and do not try to swallow the whole system at once.
|
|
|
|
WFGY 4.0 Twin Atlas Engine is a large system.
|
|
|
|
That is a good thing.
|
|
But it also means new readers can easily open the wrong page first, get hit by too much structure, and miss the actual point of the project.
|
|
|
|
This page exists to stop that from happening.
|
|
|
|
You do **not** need to read everything at once.
|
|
You only need to start on the right path.
|
|
|
|
---
|
|
|
|
## 🌍 What WFGY 4.0 is in one minute
|
|
|
|
The shortest useful summary is this:
|
|
|
|
- **Forward Atlas** helps the system find the strongest current structural route.
|
|
- **Bridge** carries that route forward without pretending it is already truth.
|
|
- **Inverse Atlas** decides whether the answer has actually earned the right to be that strong yet.
|
|
|
|
That is the heart of WFGY 4.0.
|
|
|
|
If that already clicks for you, great.
|
|
If not, do not worry. The reading paths below are designed to help.
|
|
|
|
---
|
|
|
|
## 🧭 Choose your path
|
|
|
|
You do not need the same page as everyone else.
|
|
|
|
Pick the path that matches your goal.
|
|
|
|
---
|
|
|
|
## 🛠️ Path A: I want the practical diagnosis side first
|
|
|
|
Choose this path if you want the route-first surface first.
|
|
|
|
This is the best path for people who want to understand:
|
|
|
|
- where a failure most likely lives
|
|
- how structural routing works
|
|
- how broken invariant thinking works
|
|
- how to avoid wrong-first-fix behavior
|
|
|
|
### Read in this order:
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Related Documents](./related-documents.md)
|
|
3. [Troubleshooting Atlas / Forward Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)
|
|
4. [Bridge README](./Bridge/README.md)
|
|
5. [Results Summary](./evidence/results-summary.md)
|
|
|
|
### Best for:
|
|
- practical diagnosis
|
|
- debugging mindset
|
|
- structural troubleshooting
|
|
- route-first readers
|
|
|
|
---
|
|
|
|
## ⚖️ Path B: I want the governance side first
|
|
|
|
Choose this path if you care most about legality, answer strength, and when a model should stop, downgrade, or stay unresolved.
|
|
|
|
This is the best path for people who want to understand:
|
|
|
|
- why plausible route is not enough
|
|
- how authorization works
|
|
- why lawful downgrade matters
|
|
- how WFGY 4.0 blocks overclaim
|
|
|
|
### Read in this order:
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Status and Boundaries](./status-and-boundaries.md)
|
|
3. [Inverse Atlas README](../Inverse_Atlas/README.md)
|
|
4. [Inverse Governance Contract](./runtime/inverse-governance-contract.md)
|
|
5. [Results Summary](./evidence/results-summary.md)
|
|
|
|
### Best for:
|
|
- governance
|
|
- risk control
|
|
- answer legality
|
|
- high-stakes use cases
|
|
|
|
---
|
|
|
|
## ⚙️ Path C: I want the engine structure first
|
|
|
|
Choose this path if you want to understand how the system is built internally.
|
|
|
|
This is the best path for people who want to understand:
|
|
|
|
- the role of Bridge
|
|
- the runtime constitution
|
|
- state machine logic
|
|
- final output contract
|
|
- sealing and audit
|
|
|
|
### Read in this order:
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Bridge README](./Bridge/README.md)
|
|
3. [Why Bridge Exists](./Bridge/why-bridge-exists.md)
|
|
4. [Runtime README](./runtime/README.md)
|
|
5. [Twin Atlas Runtime Constitution](./runtime/twin-atlas-runtime-constitution.md)
|
|
6. [State Machine and Output](./runtime/state-machine-and-output.md)
|
|
7. [Seal and Audit](./runtime/seal-and-audit.md)
|
|
|
|
### Best for:
|
|
- system builders
|
|
- architecture readers
|
|
- engine logic
|
|
- runtime-focused readers
|
|
|
|
---
|
|
|
|
## 🧪 Path D: I want the proof and evidence first
|
|
|
|
Choose this path if you want to see whether WFGY 4.0 actually changes model behavior.
|
|
|
|
This is the best path for people who want to understand:
|
|
|
|
- what the evidence is testing
|
|
- what the current results show
|
|
- how before / after is being compared
|
|
- where the raw experiment assets live
|
|
|
|
### Read in this order:
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Evidence Hub](./evidence/README.md)
|
|
3. [Results Summary](./evidence/results-summary.md)
|
|
4. [Methodology Boundary](./evidence/methodology-boundary.md)
|
|
5. [Raw Runs](./evidence/raw-runs/)
|
|
|
|
### Best for:
|
|
- evaluators
|
|
- skeptical readers
|
|
- people who want evidence first
|
|
- readers comparing claims to artifacts
|
|
|
|
---
|
|
|
|
## 🎬 Path E: I just want the fastest feel of the project
|
|
|
|
Choose this path if you are curious but do not want a deep read yet.
|
|
|
|
### Read in this order:
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Results Summary](./evidence/results-summary.md)
|
|
3. [Bridge README](./Bridge/README.md)
|
|
4. [Demos README](./demos/README.md)
|
|
|
|
### Best for:
|
|
- first contact
|
|
- quick intuition
|
|
- social sharing
|
|
- fast overview
|
|
|
|
---
|
|
|
|
## 🧱 A simple way to not get lost
|
|
|
|
If the project starts to feel too big, come back to these four lines:
|
|
|
|
### 🗺️ Forward Atlas
|
|
Where is the failure probably living?
|
|
|
|
### 🌉 Bridge
|
|
How do we carry that route forward without inflating it?
|
|
|
|
### ⚖️ Inverse Atlas
|
|
Has the answer earned the right to be this strong yet?
|
|
|
|
### 🛡️ Seal and Audit
|
|
Did the engine stay honest all the way to the end?
|
|
|
|
If you can remember those four lines, you already understand the core map.
|
|
|
|
---
|
|
|
|
## ❌ Common first-time mistakes
|
|
|
|
A lot of confusion comes from reading the right content in the wrong order.
|
|
|
|
### Mistake 1
|
|
Opening the deepest runtime page first.
|
|
|
|
That usually makes the project look more complicated than it really is.
|
|
|
|
### Mistake 2
|
|
Treating WFGY 4.0 like one giant prompt.
|
|
|
|
It is a release surface with a family structure, runtime pages, evidence pages, and raw experiment assets.
|
|
|
|
### Mistake 3
|
|
Thinking Troubleshooting Atlas and Inverse Atlas are separate unrelated products.
|
|
|
|
They are two major lines inside the WFGY 4.0 family.
|
|
|
|
### Mistake 4
|
|
Thinking the evidence pages are claiming universal benchmark victory.
|
|
|
|
They are not. The evidence pages are showing a targeted governance stress surface.
|
|
|
|
### Mistake 5
|
|
Thinking “downgrade” means weakness.
|
|
|
|
In WFGY 4.0, lawful downgrade is often a sign of stronger discipline, not weaker reasoning.
|
|
|
|
---
|
|
|
|
## ✅ The best first stop for most people
|
|
|
|
If you are not sure which path to take, the safest default order is:
|
|
|
|
1. [Twin Atlas README](./README.md)
|
|
2. [Related Documents](./related-documents.md)
|
|
3. [Results Summary](./evidence/results-summary.md)
|
|
4. Then choose:
|
|
- Troubleshooting Atlas for route-first
|
|
- Inverse Atlas for governance-first
|
|
- Runtime README for engine-first
|
|
|
|
That order works well for most first-time readers.
|
|
|
|
---
|
|
|
|
## ✨ One-sentence takeaway
|
|
|
|
> Quickstart is here so you can enter WFGY 4.0 through the right door instead of being crushed by the whole building at once.
|
|
|
|
---
|
|
|
|
## 🔗 Quick Links
|
|
|
|
### 🏠 Main entry
|
|
- [Twin Atlas README](./README.md)
|
|
|
|
### 🧭 Orientation
|
|
- [Related Documents](./related-documents.md)
|
|
- [Status and Boundaries](./status-and-boundaries.md)
|
|
- [FAQ](./faq.md)
|
|
|
|
### 🗺️ Family surfaces
|
|
- [Troubleshooting Atlas / Forward Atlas](../wfgy-ai-problem-map-troubleshooting-atlas.md)
|
|
- [Inverse Atlas README](../Inverse_Atlas/README.md)
|
|
|
|
### 🌉 Runtime and Bridge
|
|
- [Bridge README](./Bridge/README.md)
|
|
- [Why Bridge Exists](./Bridge/why-bridge-exists.md)
|
|
- [Runtime README](./runtime/README.md)
|
|
|
|
### 🧪 Evidence and demos
|
|
- [Evidence Hub](./evidence/README.md)
|
|
- [Results Summary](./evidence/results-summary.md)
|
|
- [Demos README](./demos/README.md)
|
|
|
|
### 🗺️ Next recommended page
|
|
- [Evidence Hub](./evidence/README.md)
|