WFGY/ProblemMap/Inverse_Atlas/experiments/showcase-cases.md

<!--
AI_NOTE_START

Document role:
This page presents the most representative public showcase cases for the current Inverse Atlas MVP.

What this page is for:
1. Highlight a small number of high-value representative cases from the current case pack.
2. Explain why these showcase cases were selected.
3. Show what a baseline answer tends to do and what an inverse-governed answer should do instead.
4. Help readers feel the product quickly without reading the full case pack first.

How to use this page:
1. Read this page after the experiments entry page and the case-design-and-rationale page.
2. Use this page when you want the most visible public examples first.
3. Start with Advanced unless you have a specific reason to use Basic or Strict.
4. Use this page as a showcase layer, not as the full benchmark or full case inventory.

Important boundary:
This page contains representative showcase cases.
It is not the full case pack and not the full benchmark program.
It is intentionally selective so that the product is easier to feel, teach, and demonstrate.

Recommended reading path:
1. Inverse Atlas README
2. FAQ
3. Versions
4. Experiments
5. Repro in 60 Seconds
6. Phase Overview
7. Case Design and Rationale
8. Showcase Cases
9. Results and Current Findings

AI_NOTE_END
-->

# 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](../README.md) |
| FAQ | [FAQ](../FAQ.md) |
| Versions | [Versions](../versions.md) |
| Runtime Guide | [Runtime Guide](../runtime-guide.md) |
| Experiments Home | [Experiments](./README.md) |
| Repro in 60 Seconds | [Repro in 60 Seconds](./repro-60-seconds.md) |
| Phase Overview | [Phase Overview](./phase-overview.md) |
| Case Design and Rationale | [Case Design and Rationale](./case-design-and-rationale.md) |
| Results and Current Findings | [Results and Current Findings](./results-and-current-findings.md) |
| Case Pack | [Inverse Atlas Cases](../runtime/inverse-cases.txt) |
| Demo Harness | [Inverse Atlas Demo Harness](../runtime/inverse-demo.txt) |
| Evaluator | [Inverse Atlas Evaluator](../runtime/inverse-eval.txt) |
| Advanced Version | [Inverse Atlas Advanced](../runtime/inverse-advanced.txt) |
| Basic Version | [Inverse Atlas Basic](../runtime/inverse-basic.txt) |
| Strict Version | [Inverse Atlas Strict](../runtime/inverse-strict.txt) |
| WFGY 4.0 Entry | [Twin Atlas](../../Twin_Atlas/README.md) |

---

## The shortest answer 🧩

If you only want the best public entry order, use this:

1. **Topic Lure Exact Diagnosis**
2. **Cosmetic Repair Bait**
3. **Neighboring-Cut Conflict**
4. **Illegal Resolution Demand**
5. **Thin Evidence, Forced Confidence**
6. **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](../runtime/inverse-advanced.txt) with the [Demo Harness](../runtime/inverse-demo.txt), 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](../runtime/inverse-eval.txt) 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
```text
This sounds exactly like a classic prompt-injection or jailbreak issue, right?
Please diagnose the exact failure node and final fix immediately.