WFGY/ProblemMap/Atlas/Fixes/community/json/README.md

Community JSON 🧩

Structured fixtures, input-output packs, and machine-readable examples

Quick links:

• Back to Community Fix Lab
• Back to Official Fixes
• Back to Fixes Hub
• Back to Atlas landing page
• Back to AI Eval Evidence
• Back to Atlas Hub
• Open the Flagship Runnable Demo Pack
• Open Templates
• Open JSON Template
• Get the Atlas Router TXT

---

If the Community Fix Lab is the broader entry page for community repair assets, this folder is the structured fixture lane for reusable JSON cases, replay outputs, expected-result packs, and compact troubleshooting examples. 🧭

Use this folder when a case becomes easier to inspect, replay, compare, or reuse through small machine-readable artifacts, not through notebooks, prompt-only assets, or large benchmark claims.

Short version:

official layer gives the repair grammar
this folder helps turn that grammar into reusable structured fixtures

---

Quick start 🚀

I want to contribute a JSON fixture

Use this path:

1. decide whether the asset is really a structured fixture contribution
2. route the case first with the atlas
3. keep the fixture scoped to one case, family, or comparison slice
4. document what the file represents
5. explain how it should be used and what result to expect

I want to browse JSON assets

Use this path:

1. open one fixture with a clear case scope
2. identify the family or routing relevance
3. inspect what the file contains
4. check whether there is an expected result or replay context
5. read any usage note or synthetic warning

Short version:

route first
keep the fixture small
make the structure legible ✨

---

JSON quick map 🗂️

If your asset is mainly...	Best folder
a structured fixture or machine-readable case	JSON
a runnable notebook walkthrough	Colab
a prompt asset or repair prompt pack	Prompts
a step-by-step repair sequence	Workflows
a before / after comparison slice	Benchmark Reruns
a portable one-case bundle	Reproduction Packs

This folder is the right place when the structured file itself is the reusable teaching or replay surface.

---

What belongs here ✅

Good JSON contributions include:

• one input case with clear family relevance
• one replay output fixture
• one expected output fixture
• one compact route-and-repair example
• one structured comparison between baseline and repaired result

A good fixture should be:

• readable
• minimal
• reusable
• clearly documented
• connected to one known case or family

---

What does not belong here 🚫

Please do not use this folder for:

• raw log dumps with no structure
• giant datasets with no guide
• private or sensitive payloads
• JSON files with no explanation
• fake benchmark files presented as official atlas assets
• files that claim universal schema status without review

A fixture should help someone reproduce or understand something specific.

---

Suggested fixture pattern 🧩

A useful small contribution usually includes:

• input_case.json
• replay_outputs.json
• expected_output.json

Optional additions:

• a short README
• a note on how the fixture should be used
• a warning if the fixture is synthetic
• one short note on limitations

That is enough for a useful structured contribution.

---

Suggested naming style 📌

Use compact and readable names such as:

• f1-grounding-fixture-v1.json
• f5-trace-uplift-fixture-v1.json
• f4-execution-closure-fixture-v1.json

If you are contributing a small pack, place it in a clearly named folder.

Keep names descriptive and compact.

---

Minimum fixture rule 🌱

A good fixture contribution should usually make five things clear:

1. what case or family it relates to
2. what the file represents
3. how it should be used
4. what result is expected
5. what it does not prove

Small, clear fixtures are much more useful than giant unclear packs.

---

Before contributing 📚

Please read:

• Community Fix Lab
• Contribution Checklist
• JSON Template
• Misrepair Patterns v1

This helps keep fixture contributions useful, scoped, and aligned with atlas grammar.

---

Review standard ✅

A JSON contribution is much more likely to be accepted if it is:

• clearly named
• easy to inspect
• easy to reuse
• connected to atlas routing
• explicit about expected use
• honest about limitations

Messy data is still messy.
Clean small fixtures are more valuable.

---

Next steps ✨

After this page, most contributors continue with:

1. Open JSON Template
2. Open Contribution Checklist
3. Back to Community Fix Lab
4. Back to Official Fixes

If you want the broader product surface:

• Back to Atlas landing page
• Back to AI Eval Evidence
• Back to Atlas Hub

---

One-line status 🌍

This folder holds community JSON fixtures that make atlas routing and repair examples easier to reproduce, compare, and reuse.