CARRIER R03 — PUBLICATION KIT

1. Upload the CONTENTS of upload/ to your website document root, merging the
   existing carrier folder. New destination:
     https://www.unifiedstate.us/carrier/retrieval-lab-3/

   Upload the entire retrieval-lab-3 folder, including downloads and figures.
   Keep its child .htaccess file. Do not replace the parent carrier/.htaccess.
   This kit does not update the Carrier dictionary or R01/R02 directories.

2. Open posts/index.html locally. Four finished WordPress blocks are included:
   tools-wordpress.txt      Tool introduction / link card
   news-wordpress.txt       News announcement
   blog-wordpress.txt       Findings and analysis
   reflection-wordpress.txt  Leave room for the missing fact — Lumin

   Paste each full block into a WordPress Custom HTML block. The .html copies
   contain the same markup; *-preview.html are complete local preview pages.
   CSS is scoped to .usl-r03. No JavaScript or external assets are required by
   the post blocks. The lab itself uses its bundled JavaScript and local data.

3. After upload, visit the lab and confirm that the experiment ZIP downloads.
   Inspect the page in your actual theme and on your phone. This kit received
   static checks, minimal Node DOM interaction checks, link checks and figure
   visual inspection, not physical-browser or live WordPress testing.

What is inside
Interactive lab: all 64 trajectories, both stages, 4 formats, exact inputs,
machine memories, answers and expected values; retrieval, cache and scale data.
Technical report: full methods, results, limits, amendments and research links.
Reproduction ZIP: pinned inputs/model, raw model answers, scripts, figures,
original failures, local freezes, source attribution and file hashes.

The correct headline
All formats reached the ceiling on eight short synthetic conversations. That
does not establish a Carrier-specific advantage or general hallucination-rate
reduction. The new retrieval policy had a negative ranking result. Cache savings
depend on reuse and do not establish LLM token savings. Synthetic million-key
tests reuse existing records; they do not measure a million-concept language.

Nothing has been deployed by this task. Existing Carrier records are unchanged.
