Two-way wire format between humans and models.

Attention budgets and source grounding built in. One IR, two lowerings — outbound brief, inbound LLM context-pack. Markdown is for storage. EOM is for dialogue.

Try the live demo → GitHub →
52%benchmark token reduction
32gold-corpus docs
H1–H12formal validators

Markdown is for storage.

EOM is for dialogue.

Today, every human–AI exchange is a flat byte stream: walls of Markdown going one way, walls of model output coming back. Both sides re-derive what matters every turn. EOM carries salience, grounding, and structure on the wire, so neither side has to.

Architecture

One core IR. Two asymmetric dialects. Shared validator.

[ Core IR ] outbound dialect inbound dialect AI → human human → AI HTML newspaper mobile cards slide deck LLM context-pack retrieval payload tool-call payload Same blocks underneath. Different projections out.

Inbound benchmark

Three documents, fifteen questions, two contexts per question. Same downstream model on both cells. Real numbers off a live run.

rawpackΔ
GDPR5,1593,239-37%
Paris 20247,4882,348-69%
RFC 9293 (TCP)3,4852,090-40%
Total16,1327,677-52%

Editorially lossy by design. Tier-A always survives. Tier-C compresses. Tier-D drops.

What it runs on

Cloudflare Workers Suite

Pages + Workers + R2 (gold corpus) + D1 (qsets + benchmark results) + KV (pack cache) + Workers AI binding.

R2 · D1 · KV · AI · Pages · Workers
Compiler frontend

Gemma-4-E4B fine-tuned via Unsloth on Modal A100-80GB. r=32, α=32, bf16, 30 epochs, canonical Unsloth recipe.

Unsloth · Gemma 4 · Modal · LoRA
Inbound LLM

OpenRouter (BYO key) routes /api/ask to google/gemma-4-31b-it. The Ask AI tab is zero-cost-to-host: judges paste their own sk-or-….

OpenRouter · BYO key

See it run.

Five tabs. Three pre-compiled samples. Live OpenRouter Q&A.

Open the demo →

Spec at docs/SPEC-v0.2.md · Writeup at docs/KAGGLE-WRITEUP.md · Source on GitHub