One question, every source I need

"Why are payments failing?" isn't a code question or a monitoring question — it's both. The answer lives in the code path and in the errors your systems are reporting right now.

I read across your sources, then answer in one place

When you ask me something, I look at whatever I've been connected to:

• Your repositories — the code that actually runs.
• Your API specs and docs — OpenAPI, Swagger, README files, internal guides.
• The tools you connect — so an answer can reflect real behaviour, not just intent.

Then I bring it together and answer in Slack, in words a non-engineer can act on — with links back to exactly where I found each part.

Why sources matter

A confident answer with no receipts is just a rumour. I show you where every claim comes from, so you can trust it, forward it, or double-check it. That's the difference between a code-search box and something your teammates can actually rely on.