SQL factory POCReport-ready candidate2026-07-02

Qwen3-0.6B Routed SQL Specialist

This is the cleanest current proof of the factory thesis: a tiny 0.6B model can beat a small public SQL baseline on a frozen exact-match slice, but only the routed artifact survives both public and execution-style gates.

Headline Numbers

Evidence class applies to each value: measured = retained evaluation or runtime result; historical = recorded result not freshly reproduced; derived = calculated or decided from records; observed = current artifact state; not-measured = an explicit evidence gap.

Public exact

0.53164-row b-mc2/sql-create-context slicemeasured

T5-small baseline

0.484same 64 public rowsmeasured

Synthetic execution

0.86050 heldout SQLite rowsmeasured

Synthetic exact

0.840same 50 heldout rowsmeasured

Competitive Context

SystemMetricScoreSize / ClassComparable?Readout
posttrainllm routed SQL v1b-mc2 exact / synthetic exec0.531 / 0.8600.6B base + 2 routed LoRAsDirectCurrent local candidate; public exact and synthetic execution gates are both frozen.
T5-small local baselineb-mc2 exact0.484~60MDirectSame 64-row public slice; posttrainllm is +4.7 points exact on this narrow gate.
Defog SQLCoder-7B-2Defog SQL-Eval category scores77.1-96%7BDirectionalStrong public SQL specialist, but reported as category-level Defog SQL-Eval scores rather than this b-mc2 slice.
Snowflake Arctic-Text2SQL-R1-7BBIRD execution accuracy68.47%7BNot comparableUseful target class for public SQL execution; posttrainllm must add a BIRD/Spider execution gate before claiming this lane.
Snowflake Arctic-Text2SQL-R1-14B / 32BBIRD execution accuracy70.04% / 71.83%14B / 32BNot comparableShows the current public high bar: execution accuracy, not exact string match.

Direct rows share this artifact's eval setup. Directional rows are useful market context but should not be read as leaderboard claims.

Adapter comparison

SetupPublic exactSynthetic execDecision
Public v4 only0.5310.240Route required
Blend v10.2970.560Reject
Best static composition0.5160.460Reject
BIRD + b-mc2 v50.4380.280Reject
Classifier-routed v10.5310.860Current best

Router verification

CheckResultEvidence
Unlabeled mixed rows11464 public / 50 synthetic
Public route reason64known_public_source
Synthetic route reason50sqlite_db_field
Route confidence>= 0.99all smoke rows

Output-hygiene DPO retries (composed, 50 heldout rows)

RunExecutionClean-SQLDecision
Frozen baseline (SFT)0.8600.000reference
2026-07-04 ref-free SimPO0.0800.000retry-training (collapse)
2026-07-11 ref-anchored DPO0.9000.000retry-training
2026-07-11 higher-pressure DPO0.9200.000retry-data

Release Blockers

Public execution benchmark missing

b-mc2 exact match is useful, but serious SQL claims need execution accuracy on public DBs.

Unblock: Add BIRD Mini-Dev SQLite or Spider SQLite execution fixtures once the DB bundle is local.

Output hygiene (raw completions carry an Answer:/Explanation: wrapper)

Two reference-anchored DPO retries (2026-07-04 SimPO collapse → fixed; 2026-07-11 gentle + higher-pressure) improved execution 0.860 → 0.900 → 0.920 but left the clean-SQL raw rate at 0.000. The wrapper is a base-model prose prior a rank-4 preference adapter can't strip — the 108 SFT targets are already bare SELECT. Composed DPO is ruled out for hygiene.

Unblock: Generation-strength fix, not more DPO: stronger SFT (higher rank / more examples) or inference-time steering (constrained SELECT-prefix decoding / stop sequence). Execution is not the problem; only the wrapper is.

Not a specialist package yet

The adapters currently live under gitignored run folders, not package metadata.

Unblock: Package under specialists/ only after a ship decision on a public execution gate.

Fine-Tune Report Card

The portable before/after proof for this artifact: baseline, candidate, deltas, regressions, slices, performance, eval validity, and the ship/retry/reject decision — with every value labeled measured, derived, historical, skipped, or not recorded. Compiled offline from the recorded factory evidence; no model was run to produce it.

Report only — no model to useNot fully verified — see the report card for why

Evidence

Next Release Action

Keep the published report artifact report-only. Two hygiene DPO retries proved reference anchoring cures the SimPO collapse and even lifts execution to 0.920, but output hygiene needs a generation-strength fix (stronger SFT or constrained SELECT-prefix decoding), not more preference tuning. Do not present it as a shipped SQL model until public execution and clean-output gates pass.