From 98da63a19aaf0c67ec6ebf08b044b92bc5eca3ae Mon Sep 17 00:00:00 2001 From: PSBigBig + MiniPS Date: Thu, 12 Mar 2026 23:45:36 +0800 Subject: [PATCH] Create README.md --- .../Atlas/Fixes/community/colab/README.md | 132 ++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 ProblemMap/Atlas/Fixes/community/colab/README.md diff --git a/ProblemMap/Atlas/Fixes/community/colab/README.md b/ProblemMap/Atlas/Fixes/community/colab/README.md new file mode 100644 index 00000000..8490b2c6 --- /dev/null +++ b/ProblemMap/Atlas/Fixes/community/colab/README.md @@ -0,0 +1,132 @@ + + +# Community Colab + +## Notebook-based community demos and runnable repair assets + +This folder is for community-contributed notebooks that help demonstrate atlas routing, first repair moves, or reproducible troubleshooting flows. + +Typical contributions here include: + +- small Colab demos +- notebook-based repair walkthroughs +- replay-first teaching notebooks +- route-first, repair-second examples +- compact reproductions of one atlas case + +--- + +## What belongs here + +Good contributions for this folder include: + +- a notebook that demonstrates one family-level repair pattern +- a notebook that replays one case clearly +- a notebook that compares baseline and repaired outputs +- a notebook that explains one boundary cut through runnable examples +- a notebook that shows atlas routing before a deeper WFGY step + +A notebook here should be: + +- small enough to understand +- easy to run +- clearly scoped +- tied to one clear routing logic +- honest about what it does and does not prove + +--- + +## What does not belong here + +Please do not use this folder for: + +- giant experimental notebooks with no explanation +- notebooks with no routing context +- notebooks that require many hidden manual steps +- random prompt playgrounds with no case framing +- notebooks that pretend to be official flagship demos + +If the notebook is not clearly connected to atlas routing, it probably belongs somewhere else. + +--- + +## Suggested notebook pattern + +A good notebook usually includes: + +1. short experiment description +2. case or family target +3. routing expectation +4. baseline behavior +5. repaired behavior +6. short result interpretation +7. expected output or success note + +That is enough for a useful community notebook. + +--- + +## Recommended file pattern + +A clean contribution can look like this: + +- one notebook file +- one short README section inside the notebook or next to it +- one small fixture if needed +- one clear expected result note + +Suggested naming style: + +- `f1-grounding-demo-community-v1.ipynb` +- `f5-observability-trace-demo-v1.ipynb` +- `f7-container-repair-demo-v1.ipynb` + +Keep names descriptive and compact. + +--- + +## Before contributing + +Please read: + +- [Community Fix Lab](../README.md) +- [Contribution Checklist](../../templates/contribution-checklist.md) +- [Colab Template](../../templates/colab-template.md) +- [Family Fix Surface v1](../../official/family-fix-surface-v1.md) + +This helps keep notebook contributions aligned with atlas grammar. + +--- + +## One-line status + +**This folder holds community notebooks that turn atlas repair grammar into runnable teaching or troubleshooting assets.**