Community JSON

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

This folder is for community-contributed JSON assets that support atlas routing, repair demonstrations, benchmark reruns, or reproducible troubleshooting examples.

Typical contributions here include:

input cases
replay output fixtures
expected output fixtures
small route-first JSON packs
compact machine-readable troubleshooting examples

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

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

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.

Before contributing

Please read:

This helps keep fixture contributions useful and aligned.

One-line status

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

3.1 KiB Raw Blame History