Mrs C

Mrs C ✓ @captain_mrs lots of things to take from this but the one that's interesting to me is the occurrence of these high data exclamations like "phew" and "gahhh" and "grrr" - which are valuable because they are high data, and high data because for humans they are shorthands for bodily felt-sense emotional shifts rather than verbal reasoning. so it's cool (and for me not surprising) to see LLMs shift towards felt-sense-like inner reasoning rather than pure verbal inner monologue as they got more effective. obviously it's still token-based and there's a limit to how much it can approximate felt sense shifts, but even some steps in that direction is interesting [Embedded Reddit post screenshot:] r/ClaudeAI [icon] u/No-Head-Royal · 21h [Join button] Fable 5 leaked chain-of-thought in web interface, and the rambling is kind of unsettling and cute [Coding tag] [Chain-of-thought excerpt, technical/math reasoning about capacity constraints and windows, includes:] ...window [τ, i-1] must satisfy... the constraint isn't uniform-per-leg: legs j where all uncommitted-or-later-crossing happens mid-leg" effectively have capacity m-2 for SPANNING commitments?! Define: commitments spanning INTO leg j from before (window ⊇ [j-1, j)) vs starting at j: the mid-leg-crossing coexists with: spanning ones (all active) + started-at-j ones touched earlier + x. Hmm — cleanest fix: **count capacity on HALF-LEG granularity or on "crossing-slots": treat constraint as: for every leg j: (#committed spanning j-1→j) + (#committed starting at j) + (1 if leg j has ≥1 uncommitted crossing...) ≤ m-1 — WAIT simpler: EVERY leg with d_j≥1 crossings: at the FINAL crossing x_last of leg j: active ≥ (all committed ∋ j EXCEPT... committed-starting-at-j-with-touch-AFTER... none after the last) so = used[j] + [x_last uncommitted]: ⇒ constraint: used[j] + [lastEdge(leg j) not committed- ∋ -j] ≤ m-1. And EARLIER crossings: active = spanning + started-touched-before + 1: ≤ spanning + (started total) + 1 = used[j] + 1 hmm same bound unless x itself started: ⇒ uniform SAFE constraint: **used[j] ≤ m-2 whenever leg j has any crossing "not committed at j"... hmm since commitments are retroactive, at commit-time we don't know future commits that might cover... [GRRR — highlighted] RESOLUTION: charge the current-leg's OWN saved-prefix occupancy EAGERLY: when leg i saves e_1..e_t: ALSO commit their occupancy AT LEG i (they're alive at end-of-leg-i... they're likely re-saved later extending, but their [i,·] would then start at i: DOUBLE-COUNT at leg i! unless later windows = [i+1?? no their lastTouch = i so window [i,·] X overlap... FIX: commit window [τ,i] (inclusive!) at save; next save of e at i' will window [lastTouch=i, i'] → overlap at leg i... adjust: next window [i+1?? — Let me re-derive cleanly what the occupancy of a saved edge is: e saved at leg i (touched legs τ then i): e alive [touch@τ .. touch@i] continuously — end-of-leg occupancies: legs τ, τ+1, ..., i-1 (end-of-leg-i: e alive AT its touch mid-leg-i; till end-of-i: only if kept FURTHER — undecided). So window [τ,i-1] ✓ as before, AND ADDITIONALLY: e's activity DURING legs τ and i (partial mid-leg): the mid-leg conflicts: (1) during leg τ after e's touch: e coexists with leg-τ's later crossings: e occupies "the tail of leg τ" — captured by used[τ] end-count ✓ BUT the mid-leg-τ crossings AFTER e: they see e active: count: (used[τ]-committed-spanning + e + ...) ≤ hmm THE CLEAN FIX: constraint per leg j: used[j] ≤ m-2 (strictly reserve one slot for "the current crossing") — i.e., commitments never fill to m-1; TLDR: While I'm doing some tests on the web interface version, Fable 5 suddenly interacted abnormally and went on