Skip to content

docs: team OS guide (Guide 06) — strategic, scenario-driven, for eng + QA#14

Merged
smorchestraai-code merged 1 commit into
mainfrom
feat/team-os-guide
May 27, 2026
Merged

docs: team OS guide (Guide 06) — strategic, scenario-driven, for eng + QA#14
smorchestraai-code merged 1 commit into
mainfrom
feat/team-os-guide

Conversation

@smorchestraai-code

Copy link
Copy Markdown
Member

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)

  1. Why This OS Exists — philosophy + what we optimize for
  2. The Mental Model — 3-layer cognitive framework, chain as forcing function, verb boundaries
  3. Constraints to Internalize — RULE 0, 9 lessons, escalation gates, branch model, codex doctrine
  4. 12 Scenarios — the meat (Day 1, new feature, existing-project feature, bug fix, hotfix at 11pm, /smo-score 78, /smo-score 88, Lana sends back at 65, /smo-canary auto-rolled back, tempted to skip /smo-verify, QA "out of scope" dispute, inherit legacy repo without overlay) — each with Situation → Temptation → Right Path → Rule → Evidence (+ Anti-pattern where relevant)
  5. Decision Frameworks — when X vs Y matrices (bridge-gaps vs replan, patch/minor/major, careful/guard, when to ping Mamoun, Codex vs Claude)
  6. Cadences — session / PR / daily / weekly / sprint / monthly / incident
  7. Failure Modes — anti-patterns + cost
  8. When Things Go Sideways — RED dev-start, validator failures, stuck plugin, SSH issues, production incidents
  9. Appendices — 22 commands · canonical paths · server registry · 30-second pocket card
  10. Glossary

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

  • Read end-to-end (target: 25 min)
  • Verify all command refs resolve (no /smo-X that doesn't exist in v1.6)
  • Verify all SOP refs resolve (SOP-13, SOP-14, SOP-36 paths)
  • Spot check 2-3 scenarios against your own experience — do they reflect reality?

🤖 Generated with Claude Code

…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>
@smorchestraai-code smorchestraai-code merged commit 593eea1 into main May 27, 2026
1 check passed
@smorchestraai-code smorchestraai-code deleted the feat/team-os-guide branch May 27, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants