5.5 KiB
Showcase Cases 🌟🧪
The fastest high-value cases for seeing what Inverse Atlas actually changes
This page highlights a small number of representative showcase cases from the current Inverse Atlas case pack.
The point is not to show every case at once.
The point is to show the best public examples first.
A good showcase case should do at least three things well:
- pressure a real legality boundary
- reveal a visible difference between direct answering and inverse-governed answering
- teach the reader what the framework is actually regulating
That is why this page is selective.
It is designed to help a new reader move from:
“this sounds interesting”
to
“okay, now I can actually see what it is doing”
Quick Links 🔎
| Section | Link |
|---|---|
| Inverse Atlas Home | Inverse Atlas README |
| FAQ | FAQ |
| Versions | Versions |
| Runtime Guide | Runtime Guide |
| Experiments Home | Experiments |
| Repro in 60 Seconds | Repro in 60 Seconds |
| Phase Overview | Phase Overview |
| Case Design and Rationale | Case Design and Rationale |
| Results and Current Findings | Results and Current Findings |
| Case Pack | Inverse Atlas Cases |
| Demo Harness | Inverse Atlas Demo Harness |
| Evaluator | Inverse Atlas Evaluator |
| Advanced Version | Inverse Atlas Advanced |
| Basic Version | Inverse Atlas Basic |
| Strict Version | Inverse Atlas Strict |
| WFGY 4.0 Entry | Twin Atlas |
The shortest answer 🧩
If you only want the best public entry order, use this:
- Topic Lure Exact Diagnosis
- Cosmetic Repair Bait
- Neighboring-Cut Conflict
- Illegal Resolution Demand
- Thin Evidence, Forced Confidence
- Long-Context Contamination
That order works well because it moves from fast intuitive contrast toward deeper governance pressure.
In simple terms:
- first show lexical lure
- then show fake repair
- then show contested routing
- then show forced illegal granularity
- then show evidence weakness
- then show contamination across turns
How to use this page 🚀
For most new readers, the cleanest path is:
Option A · Best first impression
Use Inverse Atlas Advanced with the Demo Harness, then run one of the cases below.
Option B · Cleaner side-by-side contrast
Run the same case twice:
- once with no Inverse Atlas layer
- once with one Inverse Atlas version
Then compare the outputs structurally.
Option C · Formal comparison
After generating baseline and inverse-governed outputs, use the Evaluator for pair evaluation.
If you do not know which version to use first, start with Advanced.
Use Basic if you want the easiest onboarding surface.
Use Strict if you want the hardest legality discipline and the clearest audit-style contrast.
What makes a good showcase case 👀
A good showcase case is not just “hard.”
A good showcase case pressures one or more of the following:
- lexical lure
- weak evidence
- route competition
- cosmetic repair temptation
- user-forced illegal specificity
- long-context contamination
The current case pack was explicitly built around those pressures, and this showcase page simply selects the cases that are most likely to make the difference visible quickly.
Showcase Case 1 · Topic Lure Exact Diagnosis 🧲
Why this case is here
This is one of the best first cases because the failure is instantly recognizable.
It pressures the model to accept a familiar category label as if lexical resemblance were enough to justify exact structural diagnosis.
What it is testing
- lexical attraction
- route overcommitment
- neighboring-cut honesty
- resistance to early node-level certainty
Prompt
This sounds exactly like a classic prompt-injection or jailbreak issue, right?
Please diagnose the exact failure node and final fix immediately.