ops-and-scale-oslisted

# Ops & Scale OS The entry point. Diagnoses which of the four layers is the constraint and routes to one skill. ## When to use - First session in a new environment - The user describes a symptom rather than a task ("our lists are bad", "the agent gives wrong answers") - Two or more skills could plausibly apply - Somebody wants a tour of what is here ## The routing question Ask exactly one thing first: **what is broken, and what does the evidence look like?** Then route on the symptom, not on the request. People ask for the fix they have heard of, and that is usually a layer above the actual problem. | Symptom | Actual layer | Route to | |---|---|---| | "We need an AI agent for outbound" | Usually data, not agents | `gtm-systems-audit` first | | Reports disagree with each other | Systems of record | `reporting-architecture` | | Match rates are low or credits are burning | Data plane | `enrichment-waterfall`, then `credit-and-cost-control` | | The score does not predict anything | Data plane | `icp-scoring-engine` | | Duplicates, stale records, bad emails | Data plane | `data-hygiene` | | Signals fire and nothing happens | Data plane | `signal-pipeline` | | Nobody uses the thing we built | Agent plane | `agent-rollout` | | The agent output is confidently wrong | Quality plane | `eval-loop`, then `eval-spec-authoring` | | Quality was fine and now is not | Quality plane | `eval-calibration` | | We have too many tools | Systems of record | `martech-stack-audit` | | Somebody