Context collector
Turn “wait, what does that mean?” into shared context.
Every team has hidden context: acronyms, historical decisions, ownership maps, and “the way we do it here.” Context Collector makes that knowledge easy to capture and easy to retrieve, so onboarding stays fast and incidents rely less on “who knows the system”.
The context that prevents unnecessary escalation.
Small, high-leverage answers that speed up ramp and reduce incident thrash.
Acronyms + terminology
Definitions, examples, and where terms show up in the system and runbooks.
Ownership + escalation
Who owns what, when to page them, and what “good handoff” looks like.
Decision history
Why a system works a certain way and what tradeoffs it was designed for.
Close to the questions, not buried in docs.
Capture and retrieve context inside your existing workflow.
Messaging integration
Ask for definitions, owners, or runbook links in your messaging platform and get answers instantly.
Runbook + incident linking
Attach context to the exact runbooks, services, and failure modes where it matters.
Structured entries
Keep entries consistent: definition, owner, links, examples, and “when it breaks” guidance.
Searchable by default
Find the answer fast: acronyms, services, owners, and common incident patterns.
A few entries teams usually need.
Use these as a starter pack to seed the knowledge base.
SLO / SLI / Error budget
What it means for your team, which dashboards matter, and when to escalate.
“Degrade mode”
What we turn off, how we toggle it, and how we verify we’re safe.
Service ownership
Primary owners, backups, vendor contacts, and escalation rules during incidents.
Known gotchas
Common failure patterns, why they happen, and the safest mitigation paths.