| .. | ||
| f1-grounding-repair-workflow-v1.md | ||
| README.md | ||
Community Workflows 🛠️
Workflow recipes, process fixes, and route-aware troubleshooting flows
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 Fix Recipe Template
- Get the Atlas Router TXT
If the Community Fix Lab is the broader entry page for community repair assets, this folder is the workflow lane for step-by-step troubleshooting sequences, route-aware repair processes, and small operational playbooks. 🧭
Use this folder when a contribution is mainly about the sequence of moves needed to go from atlas routing into a usable repair process, not when the contribution is mainly a notebook, JSON fixture, prompt pack, or official repair rule.
Short version:
official layer gives the repair grammar
this folder helps turn that grammar into repeatable troubleshooting sequences
Quick start 🚀
I want to contribute a workflow recipe
Use this path:
- decide whether the asset is really a workflow contribution
- route the case first with the atlas
- keep the workflow scoped to one family, one case, or one recurring failure pattern
- make the repair sequence explicit and readable
- explain expected output, limits, and escalation conditions
I want to browse workflow assets
Use this path:
- open one workflow with a clear routing assumption
- identify the target family or failure class
- inspect the first repair move
- inspect the follow-up checks and escalation condition
- check the expected result and known limits
Short version:
route first
keep the process scoped
make the sequence legible ✨
Workflow quick map 🗂️
| If your asset is mainly... | Best folder |
|---|---|
| a step-by-step repair sequence or troubleshooting process | Workflows |
| a runnable notebook walkthrough | Colab |
| a structured fixture or machine-readable case | JSON |
| a route-aware prompt asset or repair prompt pack | Prompts |
| a before / after comparison slice | Benchmark Reruns |
| a portable one-case bundle | Reproduction Packs |
This folder is the right place when the process itself is the main reusable troubleshooting surface.
What belongs here ✅
Good workflow contributions include:
- one repair flow for one family
- one route-then-repair sequence
- one benchmark rerun process
- one troubleshooting workflow for a known recurring case
- one escalation flow from atlas first move into deeper WFGY exploration
A good workflow recipe should be:
- scoped
- readable
- sequential
- realistic
- explicit about expected result
What does not belong here 🚫
Please do not use this folder for:
- giant architecture plans with no runnable steps
- vague “best practices” with no route or case
- workflows that skip diagnosis entirely
- workflows that claim guaranteed success without limits
- giant systems documentation unrelated to atlas use
- procedure dumps with no clear first repair logic
A workflow asset should help someone move through a troubleshooting process more clearly, not bypass routing or replace the official atlas grammar.
Suggested workflow pattern 🧩
A useful workflow recipe usually includes:
- target case or family
- routing assumption
- first repair move
- follow-up checks
- escalation condition
- expected output or success condition
This is enough for a strong community workflow contribution.
Suggested naming style 📌
Examples:
f4-execution-closure-workflow-v1.mdf5-observability-uplift-workflow-v1.mdf3-continuity-repair-workflow-v1.md
Use names that reveal both the family and the workflow intent.
Keep names readable and compact.
What a good first workflow looks like 🌱
A strong first contribution usually looks like this:
- one family
- one recurring case
- one route assumption
- one first repair move
- one follow-up check sequence
- one short explanation of when to escalate
Small, clear workflow recipes are much better than giant messy playbooks.
Before contributing 📚
Please read:
This helps keep workflow contributions aligned with atlas grammar instead of drifting into vague process writing.
Review standard ✅
A workflow contribution is much more likely to be accepted if it is:
- clearly named
- easy to follow
- easy to apply
- connected to atlas routing
- explicit about expected output
- honest about limitations
Messy process is still messy.
Clean scoped workflows are more valuable.
Next steps ✨
After this page, most contributors continue with:
- Open Fix Recipe Template
- Open Contribution Checklist
- Back to Community Fix Lab
- Back to Official Fixes
If you want the broader product surface:
One-line status 🌍
This folder holds community workflow recipes that turn atlas routing into concrete repair sequences and troubleshooting flows.