Phase 5: reposition KPIs as the community evidence engine; sharpen case-study call to proof
Fix broken module nav links: remove colon from module page slugs
GitHub's markdown sanitizer parsed 'Module-1:' in link targets as a URL
scheme and stripped the links, so all five Core Framework Module entries
rendered as plain (non-clickable) text. Rename the five module pages to
colon-free slugs (and &->and for Module 5) and update every reference
across the wiki.
Seed case-studies page with an illustrative worked example
- Add a clearly-labelled fictional example (FieldNotes) demonstrating the case-study format end to end, including the honest 'what the framework got wrong' section
- Keep the call for real, attributed community submissions
Build out complete SAE Framework wiki
- Fix broken navigation: remove Unicode-hyphen duplicate pages, normalize all filenames/links to ASCII hyphens
- Author Modules 1-5 in full from the playbook (Brooks's Law math, vertical slice, AI hygiene, SDD, Digital Org Chart, Zero-Ops stack, Context Entropy, self-healing loop)
- Add 12 Layers collapse table with legacy-vs-SAE columns
- Add toolkit pages: Getting Started, SDD Spec Template, Glossary, When NOT to Use SAE
- Add community pages: Contribution Guidelines, Approved Zero-Ops Tooling List, Solo Production Case Studies
- Add Reality Check guardrails throughout; update sidebar and footer