Upload folder using huggingface_hub
Browse files
app.py
CHANGED
|
@@ -344,10 +344,21 @@ so whether there's a carry depends on the cascade from the right).
|
|
| 344 |
abstraction tokens inserted every 4 positions (K=4).
|
| 345 |
""")
|
| 346 |
|
| 347 |
-
gr.Markdown("### 1. Token
|
| 348 |
-
|
| 349 |
-
|
| 350 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 351 |
|
| 352 |
gr.Markdown("""### 2. Causal verification: token identity matters for hard cascades
|
| 353 |
|
|
|
|
| 344 |
abstraction tokens inserted every 4 positions (K=4).
|
| 345 |
""")
|
| 346 |
|
| 347 |
+
gr.Markdown("""### 1. Token specialization by difficulty
|
| 348 |
+
|
| 349 |
+
For each token, we ask: **what kinds of problems does this token appear in?** The heatmap shows
|
| 350 |
+
P(difficulty level | token) — if a token is uniformly distributed across S0-S6, it carries no
|
| 351 |
+
difficulty-specific information. If it concentrates on specific levels, it's a specialist.
|
| 352 |
+
|
| 353 |
+
**Addition (left):** Token t3 (simple addition, 0% carry) concentrates on S0 (no cascades). Tokens
|
| 354 |
+
t8, t9 (100% carry) spread across S1-S5 — they're the carry workhorses. Token t2 peaks at S6
|
| 355 |
+
(the hardest cascade) despite having only 5% local carry — it encodes cascade *propagation*, not
|
| 356 |
+
local carry state.
|
| 357 |
+
|
| 358 |
+
**Subtraction (right):** Token t16 appears 93% in M0 (no borrows) — a pure "easy case" marker.
|
| 359 |
+
Tokens t5 and t11 shift toward M4/M5 (deep borrow cascades).
|
| 360 |
+
""")
|
| 361 |
+
gr.Image("static_figures/fig1_token_difficulty_profiles.png")
|
| 362 |
|
| 363 |
gr.Markdown("""### 2. Causal verification: token identity matters for hard cascades
|
| 364 |
|