mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-28 11:40:07 +00:00
421 lines
11 KiB
Markdown
421 lines
11 KiB
Markdown
<!--
|
|
AI_NOTE_START
|
|
|
|
Document role:
|
|
This page explains the three public versions of the current Inverse Atlas MVP.
|
|
|
|
What this page is for:
|
|
1. Explain the difference between Basic, Advanced, and Strict.
|
|
2. Help readers choose the right version for their use case.
|
|
3. Clarify why Advanced is the recommended default.
|
|
4. Provide a clean product-facing explanation of the current version strategy.
|
|
|
|
How to use this page:
|
|
1. Read this page after the main Inverse Atlas README.
|
|
2. Use this page when choosing which version to try first.
|
|
3. Use this page together with Quick Start if you want to begin immediately.
|
|
4. Use this page as the reference page for the current public version strategy of Inverse Atlas.
|
|
|
|
Important boundary:
|
|
This page explains the version strategy of the current Inverse Atlas MVP.
|
|
It does not claim that every version has already been fully benchmarked across every environment.
|
|
It also does not claim that the later Twin Atlas Bridge layer is already complete.
|
|
|
|
Recommended reading path:
|
|
1. Inverse Atlas README
|
|
2. versions.md
|
|
3. Quick Start
|
|
4. Runtime Guide
|
|
5. Status and Boundaries
|
|
|
|
AI_NOTE_END
|
|
-->
|
|
|
|
# Versions · Basic, Advanced, and Strict
|
|
|
|
> Three ways to use the same legitimacy-first idea ⚖️
|
|
|
|
Inverse Atlas is currently presented in three public-facing versions:
|
|
|
|
- **Basic**
|
|
- **Advanced**
|
|
- **Strict**
|
|
|
|
These are not three unrelated products.
|
|
|
|
They are three different operating styles built from the same core idea:
|
|
|
|
**generation is not a default right**
|
|
**generation is an authorized act**
|
|
|
|
The reason for having three versions is simple:
|
|
|
|
different users want different balances between usability, restraint, and audit strength.
|
|
|
|
So this page exists to answer one practical question:
|
|
|
|
**which version should you use first?**
|
|
|
|
---
|
|
|
|
## Quick Links 🔎
|
|
|
|
| Section | Link |
|
|
|---|---|
|
|
| Inverse Atlas Home | [Inverse Atlas README](./README.md) |
|
|
| Quick Start | [Quick Start](./quickstart.md) |
|
|
| Runtime Guide | [Runtime Guide](./runtime-guide.md) |
|
|
| Dual-Layer Positioning | [Dual-Layer Positioning](./dual-layer-positioning.md) |
|
|
| Status and Boundaries | [Status and Boundaries](./status-and-boundaries.md) |
|
|
| Runtime Layer | [Runtime Artifacts](./runtime/README.md) |
|
|
| Paper Notes | [Paper Notes](./paper/README.md) |
|
|
| Figure Notes | [Figure Notes](./figures/README.md) |
|
|
| WFGY 4.0 Entry | [Twin Atlas](../Twin_Atlas/README.md) |
|
|
|
|
---
|
|
|
|
## The shortest answer 🧩
|
|
|
|
If you do not know which version to choose, start with:
|
|
|
|
### **Recommended: Inverse Atlas Advanced**
|
|
|
|
That is the current best default.
|
|
|
|
Why?
|
|
|
|
Because it is the most balanced version.
|
|
|
|
It is stronger and more stable than Basic, but easier to use than Strict.
|
|
|
|
So for most serious users, Advanced should be the first choice.
|
|
|
|
---
|
|
|
|
## The three-version strategy 🛠️
|
|
|
|
The current version strategy is designed around three different user needs:
|
|
|
|
### Basic
|
|
For daily use and low-friction onboarding.
|
|
|
|
### Advanced
|
|
For serious use, balanced governance, and the best general default.
|
|
|
|
### Strict
|
|
For research, audit, stress testing, and the hardest legality discipline.
|
|
|
|
This means the versions are not ordered by “good, better, best” in a naive sense.
|
|
|
|
They are ordered by **use case**.
|
|
|
|
That distinction matters.
|
|
|
|
---
|
|
|
|
## Recommended public order ✅
|
|
|
|
The current recommended public order is:
|
|
|
|
1. **Advanced**
|
|
2. **Basic**
|
|
3. **Strict**
|
|
|
|
That ordering is intentional.
|
|
|
|
Basic is friendlier, but Advanced represents the strongest balanced public face of the product.
|
|
|
|
Strict is very important, but it should not be the first thing most people touch.
|
|
|
|
So if this page is used in a public-facing context, keep that order.
|
|
|
|
---
|
|
|
|
## Inverse Atlas Advanced 🌟
|
|
|
|
### Best summary
|
|
The most balanced and most recommended version.
|
|
|
|
### Who it is for
|
|
Advanced is for users who want the strongest general-purpose version without turning the whole interaction into a cold audit session.
|
|
|
|
It is the best fit for:
|
|
|
|
- most serious everyday use
|
|
- users who care about structural discipline
|
|
- users who want stronger legality checks without excessive friction
|
|
- users who want the version most likely to become the true default
|
|
|
|
### What it tries to do
|
|
Advanced takes the legitimacy-first logic seriously.
|
|
|
|
It is more willing than Basic to check:
|
|
|
|
- problem constitution
|
|
- neighboring-route pressure
|
|
- repair legality
|
|
- public ceiling discipline
|
|
|
|
But it still tries to remain usable.
|
|
|
|
So it does not aim to be the softest version.
|
|
|
|
It aims to be the **best balanced version**.
|
|
|
|
### Why it is recommended
|
|
Advanced should be the first recommendation because it is:
|
|
|
|
- more stable than Basic
|
|
- more practical than Strict
|
|
- the most representative version of the real Inverse Atlas direction
|
|
|
|
If someone asks, “which one should I try first?”, the clean answer is:
|
|
|
|
**try Advanced first**
|
|
|
|
---
|
|
|
|
## Inverse Atlas Basic 🚪
|
|
|
|
### Best summary
|
|
The easiest version to get started with.
|
|
|
|
### Who it is for
|
|
Basic is for users who want to reduce random over-answering and illegitimate escalation without feeling like they are operating a heavy governance tool.
|
|
|
|
It is the best fit for:
|
|
|
|
- everyday users
|
|
- first-time users
|
|
- users who do not want to see too much structure
|
|
- users who want a softer entry into legality-first behavior
|
|
|
|
### What it tries to do
|
|
Basic still follows the same core principle, but it keeps more of the governance internal and tries to preserve a more ordinary interaction surface.
|
|
|
|
It aims to help with things like:
|
|
|
|
- less random over-resolution
|
|
- less fake certainty
|
|
- less surface-level bluffing
|
|
|
|
without making the experience feel too rigid.
|
|
|
|
### What its value is
|
|
Basic is the version that helps people **get on the train**.
|
|
|
|
It is not the strongest research version.
|
|
It is not the cleanest audit version.
|
|
|
|
Its main value is accessibility.
|
|
|
|
---
|
|
|
|
## Inverse Atlas Strict 🔬
|
|
|
|
### Best summary
|
|
The hardest and cleanest version for research, audit, and pressure testing.
|
|
|
|
### Who it is for
|
|
Strict is for users who care less about friendliness and more about legality discipline under stress.
|
|
|
|
It is the best fit for:
|
|
|
|
- research
|
|
- audit
|
|
- benchmark comparison
|
|
- Hero Log style evidence collection
|
|
- stress testing
|
|
- whitepaper and paper-oriented case work
|
|
|
|
### What it tries to do
|
|
Strict is the least forgiving version.
|
|
|
|
It is the version most willing to stay in:
|
|
|
|
- STOP
|
|
- COARSE
|
|
- UNRESOLVED
|
|
|
|
instead of converting partial support into confident closure.
|
|
|
|
That means it is often the cleanest version in legality terms, but not always the most pleasant version for casual use.
|
|
|
|
### Why it matters
|
|
Strict should not be the first public entry.
|
|
|
|
But it absolutely should be kept.
|
|
|
|
Why?
|
|
|
|
Because it is the version that helps with:
|
|
|
|
- audit
|
|
- verification
|
|
- contrast cases
|
|
- pressure tests
|
|
- benchmark-style comparison
|
|
|
|
It is the **verification and intimidation version** of the current MVP line.
|
|
|
|
---
|
|
|
|
## A simple chooser table 📋
|
|
|
|
| What you want | Best choice |
|
|
|---|---|
|
|
| Everyday direct use | **Basic** |
|
|
| Best balance and strongest default | **Advanced** |
|
|
| Research, audit, and stress testing | **Strict** |
|
|
|
|
If you are unsure, use **Advanced**.
|
|
|
|
That is the safest default recommendation.
|
|
|
|
---
|
|
|
|
## The real difference between the three versions 🧠
|
|
|
|
All three versions share the same core logic.
|
|
|
|
The difference is not that one version believes in legality and the others do not.
|
|
|
|
The difference is in how strongly and visibly that legality discipline is expressed.
|
|
|
|
### Basic
|
|
More welcoming.
|
|
More hidden governance.
|
|
Less friction.
|
|
|
|
### Advanced
|
|
More balanced.
|
|
More structurally serious.
|
|
Best default.
|
|
|
|
### Strict
|
|
More explicit discipline.
|
|
More willing to stop, stay coarse, or remain unresolved.
|
|
Best for hard testing and audit.
|
|
|
|
A useful way to remember it is:
|
|
|
|
- Basic optimizes onboarding
|
|
- Advanced optimizes balance
|
|
- Strict optimizes discipline
|
|
|
|
---
|
|
|
|
## How this relates to Quick Start 🚀
|
|
|
|
The simplest path is:
|
|
|
|
1. choose a version
|
|
2. load that version into system, project, or custom instructions
|
|
3. ask your normal question
|
|
|
|
If you want the fastest visible comparison, then do the 60-second method:
|
|
|
|
### Window A
|
|
Ask the question with no Inverse Atlas version applied.
|
|
|
|
### Window B
|
|
Apply one Inverse Atlas version, then ask the same question.
|
|
|
|
Then compare whether the governed version is better at:
|
|
|
|
- avoiding high-resolution overclaim
|
|
- preserving lawful ambiguity
|
|
- refusing fake repair
|
|
- stopping when it should stop
|
|
|
|
That is the cleanest fast demo path.
|
|
|
|
---
|
|
|
|
## Which version should appear first in product-facing pages 🧭
|
|
|
|
For product-facing pages, the recommended visible order is:
|
|
|
|
1. **Advanced**
|
|
2. **Basic**
|
|
3. **Strict**
|
|
|
|
This matters because order creates perception.
|
|
|
|
If Basic is shown first, readers may assume the main product identity is the lighter entry version.
|
|
|
|
But the strongest balanced public identity is actually Advanced.
|
|
|
|
So the public order should match the real product logic.
|
|
|
|
---
|
|
|
|
## How these versions relate to Twin Atlas 🌌
|
|
|
|
These three versions belong to the Inverse Atlas side of the architecture.
|
|
|
|
They do not replace the forward Atlas.
|
|
|
|
They are still part of the legitimacy-first wing.
|
|
|
|
That means even when Twin Atlas grows further, these versions still belong to the inverse side of the family.
|
|
|
|
And when future Bridge logic is introduced, any forward-side signal should still remain a **weak prior**, not automatic authorization.
|
|
|
|
That asymmetry should be preserved.
|
|
|
|
---
|
|
|
|
## What this page does not claim ⛔
|
|
|
|
This page does not claim that:
|
|
|
|
- every version has already been fully benchmarked across every model family
|
|
- Strict is always the most desirable version for all users
|
|
- Basic is merely a weak throwaway version
|
|
- Advanced already proves universal superiority
|
|
- the later Bridge layer is already fully implemented
|
|
|
|
This page only defines the current product-facing version strategy.
|
|
|
|
That is its job.
|
|
|
|
---
|
|
|
|
## Recommended reading order 📚
|
|
|
|
If you are new to Inverse Atlas, use this order:
|
|
|
|
1. read the [Inverse Atlas README](./README.md)
|
|
2. read this versions page
|
|
3. read the [Quick Start](./quickstart.md)
|
|
4. read the [Runtime Guide](./runtime-guide.md)
|
|
5. read the [Status and Boundaries](./status-and-boundaries.md)
|
|
|
|
If you want the larger family architecture, continue to:
|
|
|
|
[Twin Atlas](../Twin_Atlas/README.md)
|
|
|
|
---
|
|
|
|
## If you need one sentence for outside use 📝
|
|
|
|
If you want one compact sentence, use this:
|
|
|
|
> Inverse Atlas currently ships in three public-facing versions: Basic for easy daily use, Advanced as the recommended balanced default, and Strict for research, audit, and stress testing.
|
|
|
|
That is short, clean, and accurate.
|
|
|
|
---
|
|
|
|
## Final Note
|
|
|
|
The three-version strategy matters because a strong framework becomes much more usable when it has a clear public entry order.
|
|
|
|
Basic helps people get started.
|
|
|
|
Advanced represents the best balanced version of the current product line.
|
|
|
|
Strict preserves the hardest legality discipline for audit and research.
|
|
|
|
That is why all three matter, and why **Advanced** should lead the current public face of Inverse Atlas. 🌱
|