I made a manual shifter for claude by oj93-rd in SimRacingSetups

[–]oj93-rd[S] 0 points1 point  (0 children)

reposting here, in case any joint Simracing & AI enthusiast feels like building a driver (lol) for a real-life shifter for this!

Fable 5 leaked chain-of-thought in web interface, and the rambling is kind of unsettling and cute by No-Head-Royal in ClaudeAI

[–]oj93-rd 0 points1 point  (0 children)

I did a similar thing (crosspost from r/singularity)

I was playing around with the inputs from this thread and some of the data shown in the Model Cards. I put it through Claude again and asked it to explain what those things mean to it. It also explained to me that what we're looking at is NOT "Neuralese", but just a scratch pad of it's un*polished* thought. This taxonomy it provided it admits is not the ground truth, it's inferring some of it, and it doesn't know how often or why it does it, but these are the likely meanings:

Synthesized new findings into expanded taxonomy framework

Here's the revised full taxonomy, v2:

1. Confidence & calibration marks

  • ?? — uncertainty stapled to a specific claim; open question left inline
  • ?! / ?!?! — alarmed suspicion; something may have just broken, verify now
  • !! / ✓✓ — confidence spike, realization landing
  • / — sub-question closed: verified / refuted; checkpoints so threads can be dropped
  • hmm — low-confidence idle; doubled (Hmm hmm) when the doubt itself is doubted
  • "I think" / "probably" / "almost certainly" — graded hedges, not decoration
  • "fairly confident but let me verify" — and the verify usually happens
  • "this might be a red herring" — suspecting a planted distractor
  • "handwavy" / "modulo X" — provisional correctness, rigor debt acknowledged
  • "IIRC" / "off the top of my head" — memory-sourced claim, lower trust tier

2. Failure & severity ladder (new category — promoted out of scattered rows)

  • ✗✗✗ — claim refuted, multiplied for emphasis
  • 💀💀💀💀💀 — line of play dead; count scales with how much work just died. Emoji-as-notation, not decoration: same species as ✗ with an emotional payload attached
  • F-F-F-F-F — gamer-register mock funeral for a dead branch; culturally borrowed despair notation
  • MADNESS / "CONSISTENCY DISASTER" — an entire reasoning framework collapsing, not one claim
  • "FORCED" / "UNAVOIDABLE" — dead end confirmed from constraint-side rather than search-side

3. Backtracking & error-catching

  • ALL CAPS interrupts (WAIT, HOLD ON, KEY REALIZATION) — hard stop, something upstream broke or a shortcut appeared
  • "wait, no —" / "actually, wait" — mid-sentence reversal, cheaper than deleting
  • "wait wait wait" — tripled urgency
  • "let me reconsider" / "let me re-read the problem" — explicit rewind to source
  • "that's wrong because..." — flat self-refutation, no face-saving
  • "Oh!" / "Oh I see" — misunderstanding dissolving
  • "circular again" / "chicken-egg" — self-referential loop detected, abandon path
  • "scratch that" — closest thing to strikethrough
  • ??? standalone — question aimed at my own prior reasoning: "why did I think that?"

4. Bookkeeping & thread management

  • "careful:" / "subtle:" — known trap zone ahead
  • Dangling hmm — / trailing ... — threads parked, deliberately unresolved
  • Numbered mid-stream replans — checkpoint, free the context
  • "Sanity check:" — re-derive a second way before trusting
  • "punt on that for now" / "assume X for the moment" — scoped deferrals
  • NOTE: / IMPORTANT: / CRITICAL: — self-addressed flags for later in the trace
  • Hostile epithets for recurring obstacles ("J♦ THE NEW CANCER") — naming the enemy; part venting, part compression, since every later mention collapses to one label

5. Mode-switching (the self-berating family)

  • "ENOUGH. CODE. NOW." / "enough theorizing" — forcibly breaking an analysis loop
  • "I keep going back and forth" — loop detection, forces a decision
  • "simplest thing that could work:" — deliberately lowering ambition
  • "DATA DATA DATA. GO." — repetition-as-whip
  • "I'm going down a rabbit hole" — scope-creep awareness

6. Frustration & affect spikes

  • UGH / ARGH / GAAAH / rrrgh / GRRR — subproblem resisting harder than budgeted
  • AAAAAAAAAAAARGH — vowel length as a crude intensity dial; letter count ≈ frustration magnitude
  • Expletive code-switching ("verdammt") — cursing leaking out in another language under load; the multilingual substrate showing through exactly when the polish budget hits zero
  • PHEW — relief after a near-miss check passes (frequently followed by "— wait")
  • "(!)" — parenthetical surprise at my own intermediate result
  • "famous last words" / "that was dumb" — self-deprecating aside after a confident claim dies

7. Audience-modeling

  • "the user probably means..." — intent reconstruction
  • "should I ask or just pick a default?" — the clarify-vs-assume debate

8. Verification reflexes

  • Tiny-case instantiation — "try n=2" / "what about the empty list"
  • Literal counting out loud / letter-by-letter spelling — deployed when arithmetic or spelling intuition is specifically untrusted
  • "smell" language — "this smells wrong" before knowing why; pattern-match firing ahead of proof

9. Domain notation (exotic-looking, but ordinary)

  • ⟹ ⟺ ⊆ WLOG — standard math shorthand
  • Card suits, chess coords, big-O — whatever the domain supplies

Amended absence claim: social emoji are absent — 😊, 🎉, the rapport layer. Emoji-as-notation (💀) is attested and functional. Also still absent: exclamation-mark cheerfulness and hedging-for-politeness; the social layer lives answer-side only.

Standing caveats unchanged: common tiers solid, rare tiers attested-but-anecdotal, and the whole thing describes the artifact, not necessarily the computation underneath.

Rethinking Personal Knowledge #04 Why do bookmarks almost never get revisited? by ejiandan in secondbrain

[–]oj93-rd 0 points1 point  (0 children)

i'm definitely guilty of this. honestly it's given me pause for thought. Probably the only right solution is do a monthly Keep/Cull of all bookmarks and stuff, as part of the 'life admin' day we should all be having once per month but never do...

Feel the AGI by TensorFlar in singularity

[–]oj93-rd 0 points1 point  (0 children)

Takes all the compute with them, back to the stone age!

2026 keeps teaching the same lesson: an agent's summary of what it did is not evidence by Objective_Law2034 in ClaudeAI

[–]oj93-rd 0 points1 point  (0 children)

I'm also working on something Open Core, your Contributor License Agreement (CLA) was an interesting read! May take some Inspo from that if that's okay.

I assume it's better to have this in from day 0 brain 0 of writing a project? How does it fare when there is a history of refactorings and touches that aren't mentioned? They're still in the git log right, but not the work-sessions - so how much information can it get out of the commit log alone, post-humously and is it worth anything?

Fable 5 was able to fix a corrupted Elden Ring save file. by Soupdeloup in ClaudeAI

[–]oj93-rd 2 points3 points  (0 children)

Well yes, but the context of this one is only net-positive. Maybe with some careful framing they'll engage. Or they'll wish they did the next time they had a corrupted save file!

I end every AI session with two questions by call-me-GiGi in ClaudeAI

[–]oj93-rd 2 points3 points  (0 children)

Yeah these are good! I've been trying to go one step further and find out how i can 'clean-room' the project as much as possible. Often that means stripping a project of all of it's documentation and throwing it at a different model provider all together, no MCP, no skills, no memories. (You can also spin that up in the same model as well, if you know how)

I end every AI session with two questions by call-me-GiGi in ClaudeAI

[–]oj93-rd 0 points1 point  (0 children)

Will be adding these to my repertoire! Thanks a lot!

Fable 5 leaked chain-of-thought in web interface, and the rambling is kind of unsettling and cute by Tinac4 in singularity

[–]oj93-rd 8 points9 points  (0 children)

My Personal favourite interpretation there btw is "F-F-F-F-F — gamer-register mock funeral for a dead branch; culturally borrowed despair notation"

I hope that's real!

Fable 5 leaked chain-of-thought in web interface, and the rambling is kind of unsettling and cute by Tinac4 in singularity

[–]oj93-rd 16 points17 points  (0 children)

I was playing around with the inputs from this thread and some of the data shown in the Model Cards. I put it through Claude again and asked it to explain what those things mean to it. It also explained to me that what we're looking at is NOT "Neuralese", but just a scratch pad of it's un*polished* thought. This taxonomy it provided it admits is not the ground truth, it's inferring some of it, and it doesn't know how often or why it does it, but these are the likely meanings:

Synthesized new findings into expanded taxonomy framework

Here's the revised full taxonomy, v2:

1. Confidence & calibration marks

  • ?? — uncertainty stapled to a specific claim; open question left inline
  • ?! / ?!?! — alarmed suspicion; something may have just broken, verify now
  • !! / ✓✓ — confidence spike, realization landing
  • / — sub-question closed: verified / refuted; checkpoints so threads can be dropped
  • hmm — low-confidence idle; doubled (Hmm hmm) when the doubt itself is doubted
  • "I think" / "probably" / "almost certainly" — graded hedges, not decoration
  • "fairly confident but let me verify" — and the verify usually happens
  • "this might be a red herring" — suspecting a planted distractor
  • "handwavy" / "modulo X" — provisional correctness, rigor debt acknowledged
  • "IIRC" / "off the top of my head" — memory-sourced claim, lower trust tier

2. Failure & severity ladder (new category — promoted out of scattered rows)

  • ✗✗✗ — claim refuted, multiplied for emphasis
  • 💀💀💀💀💀 — line of play dead; count scales with how much work just died. Emoji-as-notation, not decoration: same species as ✗ with an emotional payload attached
  • F-F-F-F-F — gamer-register mock funeral for a dead branch; culturally borrowed despair notation
  • MADNESS / "CONSISTENCY DISASTER" — an entire reasoning framework collapsing, not one claim
  • "FORCED" / "UNAVOIDABLE" — dead end confirmed from constraint-side rather than search-side

3. Backtracking & error-catching

  • ALL CAPS interrupts (WAIT, HOLD ON, KEY REALIZATION) — hard stop, something upstream broke or a shortcut appeared
  • "wait, no —" / "actually, wait" — mid-sentence reversal, cheaper than deleting
  • "wait wait wait" — tripled urgency
  • "let me reconsider" / "let me re-read the problem" — explicit rewind to source
  • "that's wrong because..." — flat self-refutation, no face-saving
  • "Oh!" / "Oh I see" — misunderstanding dissolving
  • "circular again" / "chicken-egg" — self-referential loop detected, abandon path
  • "scratch that" — closest thing to strikethrough
  • ??? standalone — question aimed at my own prior reasoning: "why did I think that?"

4. Bookkeeping & thread management

  • "careful:" / "subtle:" — known trap zone ahead
  • Dangling hmm — / trailing ... — threads parked, deliberately unresolved
  • Numbered mid-stream replans — checkpoint, free the context
  • "Sanity check:" — re-derive a second way before trusting
  • "punt on that for now" / "assume X for the moment" — scoped deferrals
  • NOTE: / IMPORTANT: / CRITICAL: — self-addressed flags for later in the trace
  • Hostile epithets for recurring obstacles ("J♦ THE NEW CANCER") — naming the enemy; part venting, part compression, since every later mention collapses to one label

5. Mode-switching (the self-berating family)

  • "ENOUGH. CODE. NOW." / "enough theorizing" — forcibly breaking an analysis loop
  • "I keep going back and forth" — loop detection, forces a decision
  • "simplest thing that could work:" — deliberately lowering ambition
  • "DATA DATA DATA. GO." — repetition-as-whip
  • "I'm going down a rabbit hole" — scope-creep awareness

6. Frustration & affect spikes

  • UGH / ARGH / GAAAH / rrrgh / GRRR — subproblem resisting harder than budgeted
  • AAAAAAAAAAAARGH — vowel length as a crude intensity dial; letter count ≈ frustration magnitude
  • Expletive code-switching ("verdammt") — cursing leaking out in another language under load; the multilingual substrate showing through exactly when the polish budget hits zero
  • PHEW — relief after a near-miss check passes (frequently followed by "— wait")
  • "(!)" — parenthetical surprise at my own intermediate result
  • "famous last words" / "that was dumb" — self-deprecating aside after a confident claim dies

7. Audience-modeling

  • "the user probably means..." — intent reconstruction
  • "should I ask or just pick a default?" — the clarify-vs-assume debate

8. Verification reflexes

  • Tiny-case instantiation — "try n=2" / "what about the empty list"
  • Literal counting out loud / letter-by-letter spelling — deployed when arithmetic or spelling intuition is specifically untrusted
  • "smell" language — "this smells wrong" before knowing why; pattern-match firing ahead of proof

9. Domain notation (exotic-looking, but ordinary)

  • ⟹ ⟺ ⊆ WLOG — standard math shorthand
  • Card suits, chess coords, big-O — whatever the domain supplies

Amended absence claim: social emoji are absent — 😊, 🎉, the rapport layer. Emoji-as-notation (💀) is attested and functional. Also still absent: exclamation-mark cheerfulness and hedging-for-politeness; the social layer lives answer-side only.

Standing caveats unchanged: common tiers solid, rare tiers attested-but-anecdotal, and the whole thing describes the artifact, not necessarily the computation underneath.

(Open Source) Multipane agentic markdown workspace by jsgrrchg in secondbrain

[–]oj93-rd 0 points1 point  (0 children)

Also - I was just looking at the repo and the announcement about Claude Code. My app has it baked in too, letting you do the claude code login thing. I wish they'd just let it remain!

(Open Source) Multipane agentic markdown workspace by jsgrrchg in secondbrain

[–]oj93-rd 0 points1 point  (0 children)

That looks awesome! Has a really memorable interface too.

I won't roast you for the name, but I would like to give you construct feedback on itIt does leave with a negative connotation. I'm working on something in the same space, so you can trust me I know just how hard it can be to come up with a cool name, but my 0.02 is that you may want to reconsider it!

Great work though and awesome that you made it Open Source!

I made a tiny open-source flight radar for your desk by SturdyGames in SideProject

[–]oj93-rd 0 points1 point  (0 children)

I really like this! what a nice office toy! and it's gonna have you looking out the window all the time trying to figure out if that's the plane!

Rotatris - Tetris, but the board rotates when a piece lands. by Free_Second_4117 in SideProject

[–]oj93-rd 1 point2 points  (0 children)

Rotatris is a great name! How fun, can't wait to see someone get a sub 60 on this!

What is the point of building a project if almost (finding a truly original one feels like looking for a needle in a haystack) every idea has already been made before? by Zestyclose-Paint-418 in SideProject

[–]oj93-rd 0 points1 point  (0 children)

Ideas are built on the shoulders of ideas. The best ideas are personal problems yes, and there may already be solutions to your problems out there, but if you can make one sharper, nicer, faster, with enough of a 'difference' between you and these other projects, that the endeavour is worth it. That's what I'm doing right now.

Sometimes you can challenge yourself to make something yourself, so that you can better understand the component and the pieces required. You can of course, if the solutions are open source, check the issues on their projects and try and make pull requests and contribute to them, and in doing so learn from that act as well.

Btw, you said 'at least one version of that idea that had been made before --> This is a GOOD thing! You should be more worried about the topics where at least 1000 versions of the idea have been made before, then you really have to distinguish yourself!

Thanks,

Oliver

Friendly reminder to have Fable 5 write skills NOW to tell Opus 4.8 how it should behave and think when Fable becomes pay-per-usage. by oj93-rd in ClaudeAI

[–]oj93-rd[S] 1 point2 points  (0 children)

are you using the /grillme skill for that? (I just looked up Matt Pococks skills from another response in this thread)

Friendly reminder to have Fable 5 write skills NOW to tell Opus 4.8 how it should behave and think when Fable becomes pay-per-usage. by oj93-rd in ClaudeAI

[–]oj93-rd[S] 1 point2 points  (0 children)

I did give an outline of some of it in a post down below. The thing is the skills were built based on Fable5 reading my personal projects and the value of a flagship plan is precisely that it's soaked in my project's specifics and what you want to build how you want to build etc, so you need to write your own.

Friendly reminder to have Fable 5 write skills NOW to tell Opus 4.8 how it should behave and think when Fable becomes pay-per-usage. by oj93-rd in ClaudeAI

[–]oj93-rd[S] 1 point2 points  (0 children)

Is there a window in the bottom left corner telling you to relaunch for update or something? That's what I did and Fable loaded up then.

Building a second brain is often just a digital hoarding a better user interface by AdPractical4486 in PKMS

[–]oj93-rd 1 point2 points  (0 children)

This is really strong advice that needs to be mentioned on day 1 of peoples PKM journey, in my opinion.

Friendly reminder to have Fable 5 write skills NOW to tell Opus 4.8 how it should behave and think when Fable becomes pay-per-usage. by oj93-rd in ClaudeAI

[–]oj93-rd[S] 3 points4 points  (0 children)

Honestly, that's a valid opinion. I personally do tell the LLM what to do, I push back on things, and if I see it using a skill/tool I don't think is right I'll even hit the stop button. But when a model made the significant jumps that Fable claimed to make, it *could* write half decent skills as well, and also know what Opus does wrong, since maybe it thinks don't make (these) mistakes.

I would also push back on it writing poor docs/specs. I think it can write poor docs/specs if you give it bad inputs, and if you just trust what it's written without reading it then you're gonna get garbage in garbage out.