Integrations¶
whatif is built to compose with the tools you already use, not replace them. This section covers the supported integrations and how each fits.
Source adapters (where traces come from)¶
Integration |
Status |
Page |
|---|---|---|
Langfuse |
v0.1-supported |
|
OpenTelemetry GenAI |
v0.2-planned |
- |
Arize Phoenix |
v0.2-planned |
- |
LangSmith |
v0.2-planned |
- |
Scorers¶
Integration |
Status |
Page |
|---|---|---|
Inspect AI |
v0.1-default |
|
RAGAS |
v0.2-planned |
- |
Custom (plugin) |
v0.2-planned |
- |
CI / GitOps¶
Integration |
Status |
Page |
|---|---|---|
GitHub Actions |
v0.2-wrapper Action |
|
GitLab CI |
community |
- |
Generic CI (CLI + exit codes) |
v0.1 |
covered in Path Z |
Downstream of the verdict¶
whatif emits Markdown + JSON reports and exit codes. Plug them into:
PR comments-paste the Markdown, post via
gh pr commentin your CI step.SLO platforms-Nobl9, sloth, Honeycomb consume the JSON for trend analysis.
Incident workflows-pipe failures into your on-call queue.
What whatif does not integrate with¶
By design-we want a clean boundary:
Tracers: not built in (you bring your own).
Eval frameworks: not reimplemented (we wrap them).
SLO platforms: not duplicated (we feed them).
Agent runtimes: not coupled (the runner contract is the boundary).