Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.deductive.ai/llms.txt

Use this file to discover all available pages before exploring further.

Run through this. Anything not checked is either a real gap, or a “you forgot to test it”. Fix before sharing the user docs with your team.

​
Sign in

  • You can sign in at your workspace URL (app.deductive.ai for self-serve / Team plans, or <company>.deductive.ai for Enterprise).

​
Connectors

  • At least one code source is green (typically GitHub).
  • At least one observability source is green (Datadog, Grafana, Prometheus, or New Relic).
  • At least one incidents source is green if your team uses one (PagerDuty, Incident.io, Rootly).
  • Test connection passed for every connector you set up. Not just “saved without error”.
  • No connector shows Indexing failed.

​
Cross-source smoke test

  • Asked a real question that requires multiple connectors to answer (e.g. “Summarize last week’s incidents and point at the code change that likely caused each one”). The answer cited both incidents and code, proving cross-source reasoning works.

​
Slack

  • Deductive Slack app is installed at the workspace level.
  • DM’d @Deductive and got a reply within a few seconds.
  • /invite @Deductive works in at least one channel and the bot replied to a @mention test.

​
Hand-off

​
You’re done

That’s the whole admin job. Day-to-day use (alert routing per channel, MCP install in each user’s IDE, feedback, reinforcing decision trees) is all user-track work that doesn’t require admin involvement. You’ll only come back here when you add a new tool to your stack.

​
Try this next

If you haven’t yet, run through the user-side experience yourself once. It’s the best way to know what your team is about to see, and you might catch a missing connector you’d otherwise hear about as a Slack DM.

Use Deductive → Welcome

The user-facing entry point. Take ten minutes to actually use it.