All models
Registry record · passport pending

Portfolio Router

This is a registry record without signed passport evidence. A channel label, an artifact URL, or an artifact hash does not establish a passport, hosting, loaded weights, or serving.

Registry and passport facts

BaseQwen2.5-1.5B-Instruct
Parameters1.5B
Channelcandidate
Dispositionregistry record · passport pending

Measured evaluation — v1 · eval_router.py (25 held-out routing probes)

Held-out routing96%
Base (same suite)76%
96/100
headline · committed eval report
+20
vs base (76 → 96), same suite
5/5
refusal recall 5/5

Evidence chain

  1. 01Corpus policyportfolio-router-gold v1 (525 ex · 473 train / 52 valid · synthetic+public · no customer data)No customer data, PHI/PII, or secrets in weights — scanned before training (FRAMEWORK.md data policy).
  2. 02Probe suite firsteval_router.py (25 held-out routing probes)Registered before training; the same suite scores base and adapter.
  3. 03Promotion · SoDreviewer ≠ trainer, recorded in lineage.jsonFail-closed gates: a regression cannot reach candidate; approval requires an independent reviewer.
  4. 04Ed25519 signingpubkey a97122c37f5c…97fac1e1signed 2026-06-27
  5. 05Offline verify/api/verify/portfolio-router-1_5bRe-derives the passport and re-checks the signature — no dashboard trust.

Artifact & distribution

adapter sha256 · 8650999374425d8fa54e55ddabbeb67d2998a8b55dc95500aff95c5bd665fda6
38.9 MB · weights referenced by hash, never committed
Request verified weightsHugging Face mirror — activates on release

Open the gated studio to inspect the registry workflow, eval runs, and release records. Those records remain separate from hosting, loaded-weight, and serving authority. Open the studio →