docs: team OS guide (Guide 06) — strategic, scenario-driven, for eng + QA#14
Merged
Conversation
…eering + QA
Reframes the team onboarding doc as an OS manual rather than a command
reference. Built around 12 scenarios that teach judgment, not syntax.
Structure:
Part 1 — Why This OS Exists (philosophy: tribal knowledge is a tax)
Part 2 — Mental Model (3-layer cognitive framework, chain as forcing function)
Part 3 — Non-Negotiable Constraints (RULE 0, 9 lessons, escalation gates)
Part 4 — 12 Scenarios (the meat — Day 1, new feature, bug fix, hotfix at 11pm,
score 78, score 88, handover sent back at 65, canary auto-rollback,
tempted to skip /smo-verify, QA "out of scope" dispute, inherit
legacy repo without overlay)
Part 5 — Decision Frameworks (when X vs Y)
Part 6 — Cadences (session / PR / daily / weekly / sprint / monthly / incident)
Part 7 — Failure Modes (anti-patterns w/ cost)
Part 8 — When Things Go Sideways
Part 9 — Quick Reference Appendices (22 commands · paths · servers · pocket card)
Part 10 — Glossary
Each scenario teaches: situation · temptation · right path · rule · evidence
(and where relevant, the anti-pattern).
Covers smorch-dev v1.6.0 + smorch-ops v1.1.0 — explicitly references the v1.6
auto-composition (/smo-verify, /smo-simplify, /smo-canary, /smo-document, /smo-cso)
and the plugin-meta overlay pattern.
Audience: every SMOrchestra engineer + QA, Day 1 to Day 365.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reframes the team user guide as an OS manual built around scenarios + judgment, not a command reference.
825 lines. Covers smorch-dev v1.6.0 + smorch-ops v1.1.0.
Structure (10 parts)
Why this matters
The team doc is the first thing a new hire reads. If it's a command reference, they learn syntax. If it's an OS guide, they learn judgment — and judgment is what the 5% of decisions the OS doesn't make for you require.
Every scenario maps to a real situation that's already happened (or will happen). Each one cites the rule that codifies the right answer.
Test plan
/smo-Xthat doesn't exist in v1.6)🤖 Generated with Claude Code