WFGY/ProblemMap/Atlas/Fixes/community/workflows

Community Workflows

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

This folder is for community-contributed workflow recipes that show how to move from atlas routing into a usable troubleshooting process.

Typical contributions here include:

• step-by-step repair flows
• workflow-oriented fix recipes
• route-first escalation paths
• small system troubleshooting playbooks
• procedural guidance for one clear failure class

---

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

---

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

---

Before contributing

Please read:

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

---

One-line status

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