Record the reference-free text-accuracy sweep

README.md

@@ -50,6 +50,32 @@ Only the transformer is quantized. The Qwen3-VL text encoder stays bf16 and is a
 16.3 GB of a 21.5 GB resident total, so it, not this file, decides how many reference
 images fit on a card.
 
+## Text accuracy against bf16
+
+Every LPIPS number above is measured *against* bf16, so it cannot answer "is this as good
+as bf16" — it defines bf16 as zero. This is the reference-free version: 8 seeds on each of
+two text prompts, scored by reading the rendered text against what the prompt asked for.
+
+| build | enamel notice board | neon shop sign | total |
+|---|---|---|---|
+| bf16 | 8/8 | 6/8 | **14/16** |
+| this checkpoint | 8/8 | 7/8 | **15/16** |
+
+**Indistinguishable.** One render's difference out of sixteen, which a different seed set
+would flip. The errors trade places rather than accumulating on one side: on one seed bf16
+renders the sign as "QWEN 2.1 IMAGE 1" and this checkpoint gets it right; on another this
+checkpoint appends a spurious "1$" where bf16 is clean.
+
+That is the claim worth making — **4-bit weights and activations with no measurable text
+degradation** — and not the stronger one. A single prompt where the quantized build beats
+bf16 is trajectory variance, not evidence of superiority.
+
+An automated OCR pass was tried first and discarded: tesseract returns noise on neon at
+night, and a character-error-rate above 1.0 was the giveaway that it was scoring incidental
+scene text rather than the sign. The table above comes from reading all 48 renders.
+
+`samples/` holds one render per prompt at seed 42. `seeds/` holds the full sweep.
+
 ## Requirements
 
 Packed for a specific kernel. The layout is an MMA fragment swizzle, so a different