docs(ADR-272): zero-shot tabular foundation model for RuVector (research + plan)#630
Open
shaal wants to merge 1 commit into
Open
docs(ADR-272): zero-shot tabular foundation model for RuVector (research + plan)#630shaal wants to merge 1 commit into
shaal wants to merge 1 commit into
Conversation
Research + plan (no implementation) for adding a zero-shot tabular FM to RuVector, framed as the tabular sibling of ruvector-timesfm (port + point inward at the DB's own index/SONA tuning). Key findings: - License gate: TabFM weights are non-commercial/non-redistributable -> cannot ship. TabPFN 2.5/2.6/3 likewise. TabPFN-v2 (clf+reg) is Apache-2.0 + attribution (Prior Labs License) -> shippable Track-B base. - Track A benchmark (docs/research/tabfm/track_a_benchmark.py, license-clean): shippable TabPFN-v2 zero-shot on CPU is top-or-tied on 5/6 OpenML datasets vs tuned XGBoost/HistGBM (mean rank 1.33 vs 2.83); big multiclass win on vehicle (+0.034 AUC). Verdict: GO. - Highest-impact uses: (1) core candle port, (2) row-compression tabular-row embedder (row->vector, native to the vector DB), (3) inward zero-shot autotuner (predict HNSW/IVF/quant knobs), (4) Postgres tab_predict() = local AI.PREDICT. Adds ADR-272 + docs/research/tabfm/ (plan, benchmark script, results). No product code; direction left open for maintainer decision.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #629.
Research + plan only — no product code. Adds the artifacts needed for @ruvnet to decide whether and how to add a zero-shot tabular foundation model to RuVector (the tabular sibling of
ruvector-timesfm).What's in this PR
docs/adr/ADR-272-*.md— the decision record: motivation, the license gate + pivot, the four highest-impact surfaces, two-track plan, consequences.docs/research/tabfm/PLAN.md— full write-up: TabFM architecture, licensing scorecard, crate-by-crate reimplementation map, and the Track A results.docs/research/tabfm/track_a_benchmark.py+track_a_results.json— the reproducible, license-clean benchmark and its raw output.TL;DR of the findings
vehicle. The model we're legally allowed to ship is good enough to own.tab_predict()= localAI.PREDICT.What this PR deliberately does NOT do
No crate scaffold, no weights vendored, no dependency changes. Direction (which surface first, whether to benchmark the gated v2.5/v3 ceiling, whether to eventually train our own weights) is left open for maintainer decision — merge as a research record, or use as the basis for a scoped implementation issue.
Reproducing the benchmark
(macOS: XGBoost needs
libomp; the run used the copy shipped intorch/lib. TabPFN-v2 Apache-2.0 weights auto-download; the gated v2.5/v3 columns are skipped unless a Prior Labs license is accepted — internal benchmarking is license-exempt.)