v5.0.0 — SPG-FM: one foundational model + the orchestration repair

v5.0.0 — SPG-FM: one foundational model instead of a stack

SPG-FM-1 (HF: spanguard-fm-1) — a single 1.70M char-level multi-task network trained on the full corpus-v4 union (7 languages × 18 carrier families):

• 0.0% escape on every in-domain set, in all 7 languages — agent-traffic (900 docs), extended-attacks (88 docs, all five 2026 families), extended-v4 (108 docs); doc F1 1.000 on both extended fixtures
• best payload localization in the family: span F1 0.917 / 0.901 (router stack: 0.689 / 0.612)
• hand-written OOD 10.4% escape — the v2-era ensemble number, from one 1.7M model, no router
• honest cost published: 45.4% / 26.4% over-strip on out-of-domain benign prose (doc head over-fires) — roadmap B/F attack exactly this

The orchestration repair (surfaced by the sandbox restore, fixed, re-measured):

• is_structured rebuilt to the carrier taxonomy (k=v anywhere in line, tight CSV, tabs)
• fast-v4 union-everywhere restored (every doc routes to one of three char experts)
• fm prose gating via its own document head
• fast-v4 hand-written OOD: 16.7% (v4 record) → 29.2% (broken restore) → 4.2% (repaired — all-time best for the stack); extended-attacks 7.1% → 0.0%
• broken intermediates committed (v5-fm-1504, v5-check-1514, v5-final-1519); release run v5-ship-1548

Also: measured charts (flagship bars, version ladder, 7-language matrix, cost & latency — every number traced to a committed record), world-class README, Kaggle P100 training kernel (committed, ~12k docs/min), 26 tests green.

Live: HF Space demo · models