Back to corpus
research noteexperiment writeup candidatescore 24

SAN Training Status - Verified vs Unverified

This page replaces the old "SAN Training V5" narrative. The old page stated dataset counts and validation loss as facts without pointing to local artifacts. The current rule is simple: training claims need files.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This page replaces the old "SAN Training V5" narrative. The old page stated dataset counts and validation loss as facts without pointing to local artifacts. The current rule is simple: training claims need files. This proves there is a local SAN weight artifact compatible with the binary manifest loader. It does not prove the training dataset, validation loss, or model quality by itself. - "V5 is 135,000 parameters." - "V5 trained on 5,408 real performance pairs." - "Validation loss was 0.028." - "Training ran from `/Volumes/HD1/training-phrases/train_san_v5.py`." - "The current deployed weights are from that exact run." They may be historically true, but this documentation set is now source-grounded. Historical claims need a training log, run directory, manifest, or checkpoint note. `Desktop/MotionMixApp/MASTER-TASKS.md` is more cautious than the old docs. At that checkpoint it says:

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.