The anofox extensions
The anofox DuckDB extensions emit their results as tables in a shared integration contract: each producer (ols_tidy_by, forecast_by, profile, pack_by, …) tags its output schema (terms, summary, prediction, curve, tests, obs, assignment, …). anofox-visualization knows each schema, so one call plots any of them:
LOAD anofox_statistics; LOAD anofox_visualization;SELECT anofox_plot(t) FROM ols_tidy_by('sales', region, revenue, [price, promo]) t; -- a coefficient plot per regionanofox_plot(t) picks the plot from the schema; anofox_plot_terms, _prediction, _curve, _tests, … choose it explicitly. In a dashboard, the same producers feed panels.
| Extension | What it produces | In the browser | CI conformance |
|---|---|---|---|
| anofox-statistics | regression (OLS … GLMM), survival, tests, ANOVA, calibration, bootstrap | live (Wasm build) | every contract producer |
| anofox-forecast | forecasts with intervals, backtests, decomposition | live (Wasm build) | ✔ |
| anofox-tabular | profiling, data quality, deduplication | precomputed | ✔ |
| anofox-optimize | packing, assignment, sequencing, replenishment | precomputed | ✔ |
| anofox-decide | decision models, triage | precomputed | ✔ |
Every producer of every extension is rendered in CI against the extension’s latest build (*-conformance jobs), so a contract change is caught the day it lands.
anofox-forecast and anofox-optimize also ship Claude Code plugins, whose skills write the extension’s SQL from a plain request (forecast, optimize).
One page per extension: anofox-statistics · anofox-forecast · anofox-tabular · anofox-optimize · anofox-decide. From Python and R: python-r.md. The schemas: the integration contract.