9.7 KiB
🚀 Start Here
The shortest onboarding page for new readers entering Inverse Atlas
Inverse Atlas already has multiple layers:
- main README
- runtime artifacts
- public runtime versions
- experiments
- paper
- figures
- Twin Atlas positioning
That depth is useful.
But for a first-time reader, too many entry points can create the opposite effect.
The project can look larger and emptier at the same time.
This page exists for one simple reason:
help you begin in the right place
You do not need to read the whole folder first.
You only need to choose the path that matches your goal.
🧭 Core Entry Pages
If you want the main navigation surface first, start here:
- Inverse Atlas README
- FAQ
- Versions
- Quick Start
- Runtime Guide
- Experiments Hub
- Reproduce in 60 Seconds
- Results and Current Findings
- Paper Notes
- Figure Notes
- Twin Atlas
⏱️ If You Only Have 2 Minutes
Read these three pages in order:
That is the fastest path to understand:
- what this is
- why it exists
- how to try it
If you stop there, you will still understand the project much better than someone who opens raw txt files with no guide.
⚡ If You Want the Fastest Product Feeling
Use this path:
- Versions
- choose Advanced
- Quick Start
- Reproduce in 60 Seconds
- Showcase Cases
This is the best route if your goal is:
I want to feel the difference quickly
You do not need the full paper first.
You do not need the full benchmark first.
You do not need Twin Atlas first.
Start with the contrast.
🧱 If You Want the Product Logic First
Use this path:
This is the best route if your goal is:
I want to know what this product line actually is
This path helps you understand:
- why Inverse Atlas exists
- what it is trying to regulate
- which version to use
- how the runtime layer is structured
- what is already true and what is not yet claimed
🧪 If You Want the Experiments First
Use this path:
- Experiments Hub
- Reproduce in 60 Seconds
- Phase Overview
- Case Design and Rationale
- Showcase Cases
- Results and Current Findings
This is the best route if your goal is:
I want to see how the current MVP is being tested
This path is especially useful if you care about:
- reproducibility
- case logic
- legality-centered evaluation
- current findings
- expected patterns
📄 If You Want the Theory First
Use this path:
This is the best route if your goal is:
I want the framework logic first
This path works well if you want to understand:
- why generation is treated as an authorized act
- what the legality chain is
- what the four governance states are
- why the forward side and inverse side are complementary
🌌 If You Want the Bigger Architecture
Use this path:
This is the best route if your goal is:
I want to know how this fits into WFGY 4.0
This path helps you understand:
- why the forward Atlas is route-first
- why Inverse Atlas is legitimacy-first
- why Twin Atlas is the family-level architecture
- why Bridge is an internal handoff layer rather than an unrelated extra module
🎛️ Which Version Should I Use First
If you do not want to think too hard about version choice, use this rule:
Recommended default
Advanced
Easier onboarding
Basic
Audit, pressure testing, and research
Strict
If you are unsure, do not overcomplicate it.
Start with Advanced.
🌟 What Should I Try First as a Real Demo
The simplest strong public demo route is:
- use Inverse Atlas Advanced
- use the Demo Harness
- start with Showcase Cases
- compare against a normal baseline answer
- optionally use the Evaluator
This gives the strongest early impression without forcing the reader to read every page first.
❌ What You Should Not Do First
Do not start by opening raw txt files with no guidance.
Do not start with the hardest theory page if your goal is fast product feeling.
Do not start with Twin Atlas if you still do not understand what Inverse Atlas itself is doing.
Do not confuse:
- current findings
- expected patterns
- future architecture
The project becomes much easier to understand when you enter it in the right order.
📦 If You Only Care About Downloads
If you only want the raw artifacts, go here:
But this is not the recommended first path for most readers.
The better path is still:
- understand the idea first
- then choose a version
- then reproduce one clean contrast
💻 If You Only Care About Colab
Go here:
Important:
Colab is mainly a reproduction tool.
You do not need to run Colab in order to understand the project.
The docs should already make the framework understandable.
📏 If You Want the Safest Scope Summary
Read:
These two pages are the safest places to check:
- what is already real
- what is currently observed
- what is still expected pattern
- what is not yet claimed
👥 Best First Paths by Reader Type
Curious first-time reader
I want to try it right now
I care about experiments
I care about architecture
I care about theory
📝 One-Sentence Outside Description
If you need one short sentence to describe this page, use this:
Start Here is the shortest onboarding page for Inverse Atlas, helping new readers choose the right path based on whether they want product feeling, theory, experiments, downloads, or the larger Twin Atlas architecture.
🌱 Final Note
A strong project should not require new readers to guess where to begin.
That is why this page exists.
Inverse Atlas already has enough layers to be interesting.
This page makes those layers easier to enter in the right order.
Start simple.
Pick the path that matches your goal.
Then go deeper only when you need to.