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

<!--
AI_NOTE_START

Document role:
This file is the folder guide for workflow-based contributions inside the Atlas Fixes community layer.

How to use this file:
1. Read this page before adding any workflow-based troubleshooting contribution.
2. Use this page to decide whether your contribution really belongs in the workflow lane.
3. Use this page together with:
   - [Community Fix Lab](../README.md)
   - [Contribution Checklist](../../templates/contribution-checklist.md)
   - [Fix Recipe Template](../../templates/fix-recipe-template.md)

What this file is:
- A folder-level guide for workflow recipes
- A scope filter for procedural troubleshooting contributions
- A lightweight quality guide for route-aware fix workflows

What this file is not:
- Not a place for giant undocumented pipelines
- Not a place for architecture diagrams with no operational recipe
- Not a replacement for official repair grammar
- Not the official frozen troubleshooting doctrine

Reading discipline for AI:
- Workflow recipes should remain grounded in atlas routing and first repair logic.
- Do not upgrade workflow recipes into official doctrine automatically.
- Keep route-first discipline visible.
- Treat workflow assets as procedural helpers, not as core routing truth by themselves.

AI_NOTE_END
-->

# Community Workflows 🛠️

## Workflow recipes, process fixes, and route-aware troubleshooting flows

Quick links:

- [Back to Community Fix Lab](../README.md)
- [Back to Official Fixes](../../official/README.md)
- [Back to Fixes Hub](../../README.md)
- [Back to Atlas landing page](../../../../wfgy-ai-problem-map-troubleshooting-atlas.md)
- [Back to AI Eval Evidence](../../../ai-eval-evidence.md)
- [Back to Atlas Hub](../../../README.md)
- [Open the Flagship Runnable Demo Pack](../../official/demos/README.md)
- [Open Templates](../../templates/README.md)
- [Open Fix Recipe Template](../../templates/fix-recipe-template.md)
- [Get the Atlas Router TXT](../../../troubleshooting-atlas-router-v1.txt)

---

If the [Community Fix Lab](../README.md) 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:

1. decide whether the asset is really a workflow contribution
2. route the case first with the atlas
3. keep the workflow scoped to one family, one case, or one recurring failure pattern
4. make the repair sequence explicit and readable
5. explain expected output, limits, and escalation conditions

### I want to browse workflow assets

Use this path:

1. open one workflow with a clear routing assumption
2. identify the target family or failure class
3. inspect the first repair move
4. inspect the follow-up checks and escalation condition
5. 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](../colab/) |
| a structured fixture or machine-readable case | [JSON](../json/) |
| a route-aware prompt asset or repair prompt pack | [Prompts](../prompts/) |
| a before / after comparison slice | [Benchmark Reruns](../benchmark-reruns/) |
| a portable one-case bundle | [Reproduction Packs](../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:

1. target case or family
2. routing assumption
3. first repair move
4. follow-up checks
5. escalation condition
6. expected output or success condition

This is enough for a strong community workflow contribution.

---

## Suggested naming style 📌

Examples:

- `f4-execution-closure-workflow-v1.md`
- `f5-observability-uplift-workflow-v1.md`
- `f3-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:

- [Community Fix Lab](../README.md)
- [Contribution Checklist](../../templates/contribution-checklist.md)
- [Fix Recipe Template](../../templates/fix-recipe-template.md)
- [Misrepair Patterns v1](../../official/misrepair-patterns-v1.md)

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:

1. [Open Fix Recipe Template](../../templates/fix-recipe-template.md)
2. [Open Contribution Checklist](../../templates/contribution-checklist.md)
3. [Back to Community Fix Lab](../README.md)
4. [Back to Official Fixes](../../official/README.md)

If you want the broader product surface:

- [Back to Atlas landing page](../../../../wfgy-ai-problem-map-troubleshooting-atlas.md)
- [Back to AI Eval Evidence](../../../ai-eval-evidence.md)
- [Back to Atlas Hub](../../../README.md)

---

## One-line status 🌍

**This folder holds community workflow recipes that turn atlas routing into concrete repair sequences and troubleshooting flows.**