MV-Omni

Format-standardized (v5) release of the MixtureVitae-Omni (MV-Omni) training text -- 6 shards, 1,593,222 rows. Several real data-quality fixes are included in this release (not just a text-markup change):

1. <see>/</see> wrapper fix. MV-Omni's own image-block convention wraps <seed2_N> payload tokens in <see>...</see>, which was never registered as an atomic special token (previous releases silently fell back to broken multi-piece BPE text for the wrapper tag). Renamed to the already-atomic <seed2>/</seed2> wrapper used by every other source.
2. Degenerate base64 turn dropped. MV-Omni's image-description records contain a 3-turn structure, one of which ("Give me the base64 encoding for this scene" -> a raw base64 blob) is not a learnable instruction -- this turn is dropped (~6% of turns), keeping the two real turns (image description + narration).
3. (v4, 2026-07-31) USER:/ASSISTANT: reformat bugs fixed. The v3 release's turn-splitting had two bugs affecting 64% of records combined: (a) records with a YouTube-metadata/caption preamble before the first Q: (30% of records) were left completely unconverted -- no USER:/ASSISTANT: markers at all; (b) turn-splitting required a literal "\nA: " (space after the colon), but a plain majority of real answer markers in this source have no space ("\nA:"), so those turns' real answer text was merged into the question half, leaving ASSISTANT: empty (34% of records). Both fixed with regex-based boundary matching (\s* instead of a required literal space) plus folding any preamble into the first turn's USER: side. Real content recovered: 9,654,544 real turns kept post-fix vs. ~1.7M for the same record count under the buggy v3 script (9-10x more real content).
4. (v5, 2026-08-02) <speak> never appears in a USER: turn. Per project design rule (the assistant listens and speaks; the user only ever listens), any <speak>-tagged audio block found inside a USER: ... ASSISTANT: span (a side effect of the v4 preamble-fold fix above, which could fold a raw <speak>-tagged preamble segment into the first turn's USER side) is downsampled to <listen> format in place (7 tok/frame -> 3 tok/frame: keep L0/L1a/L1b, drop the 4 L2 sub-bands -- mathematically exact, no re-encoding). <speak> legitimately on the ASSISTANT side (this source's own listen->transcribe->speak turn family) is untouched. Verified over the full corpus: 0 occurrences of <speak> inside any USER span post-fix (was present in ~13.8% of records pre-fix, consistent across all 6 shards).

On top of those fixes, the Q:/A: convention used previously is rewritten as USER:/ASSISTANT: per turn (this source is genuinely multi-turn, not single Q/A), and an empty <think>\n</think> pair is added before every assistant turn -- consistent with the other 5 sources in the training mix.

Separately (not part of this text-format pass, but relevant to anyone retokenizing this release): the previous MV-Omni tokenize predated the vocab's <listen>/<speak>/SNAC-L2-band additions, so a large fraction of <speak> audio payload silently fell back to broken multi-piece BPE text. That is a tokenizer-time issue, not present in this raw text release, but worth knowing if you tokenize this data with an older tokenizer checkpoint.

Format

USER: <prompt> ASSISTANT:
<think>
</think>
<seed2>...</seed2> / <listen>...</listen> / <speak>...</speak> (per turn, depending on modality)

Base

MixtureVitae-Omni, re-tokenized with tokenizer_vla_qwen3_v2.