Guides for the questions search cannot answer.
Practical notes on service ownership, blast radius, on-call tracking, stale documentation and the difference between a knowledge graph and RAG.
Start with the problem you have
Service ownership: a practical guide
What ownership means, the four questions an ownership system must answer, and how to keep the record current.
Read the guide →How to find the owner of a microservice
A step-by-step way to find the accountable team, verify it against three signals, and handle the unowned case.
Read the guide →Service ownership checklist
The four non-negotiables, the monthly review and the failure modes that make an ownership record go stale.
Read the guide →Service ownership tools: what to look for
The five capabilities that separate an ownership system from a spreadsheet, plus demo questions that expose weak tools.
Read the guide →Who owns this service?
Why the top committer is often the wrong answer, and the four signals that produce an owner you can act on.
Read the guide →Blast radius analysis for microservices
How to follow dependency direction, group by hop depth, and spot the unowned service that makes a cascade worse.
Read the guide →Engineering knowledge graph vs RAG
What text retrieval is good at, where similarity fails for ownership and impact, and how to combine both.
Read the guide →On-call and service ownership tracking
Why ownership and on-call are different facts, and how to keep rotations and escalation paths current.
Read the guide →How to detect stale documentation
A practical stale-doc check using verification dates, supersession edges and code-touch signals.
Read the guide →See the graph behind the guides
The demo uses the same payments-gateway company described in these articles: 185 nodes, eight downstream services and one deliberately unowned service.