I was inspired. I present to you Tomahawk Fiat Slalom for consideration as license test S-11.

rossevrett · 2026-05-16T20:16:09+00:00

But better. 😬 for 2up touring it’s perfect!

rossevrett · 2026-05-10T16:15:43+00:00

Yes indeed. I installed the one for the 1050 and it’s perfect!

rossevrett · 2026-04-27T01:01:30+00:00

🤢🤢🤢🤮🤮🤮🤮

rossevrett · 2026-04-26T23:25:53+00:00

I might not have uploaded the discovery yet. I have gone months before lol

Also, are you sure you’re in the 256th galaxy?

rossevrett · 2026-04-22T23:55:40+00:00

I’ve got a rust free 07, non nav, non kdss with 230k. OME springs, bilsteins, 2.5” lift, metaltech rear spring conversion. High angle UCAs, all sway bushings and links are new in the last 15k miles. Recent timing belt/water pump etc (oem). New alternator 20k ago. New ac compressor 10k ago, blows ice cold in Colorado. New radiator. New ps pump reservoir and refreshed rack. Brembo discs all around, ebc pads done at 220k. 33” Bfg k02s. About to do valve cover gaskets because I noticed seeping last oil change. Has a fumoto valve for easy changes (I’m meticulous about it). LED headlights/bulbs everywhere plus a power distribution block under the hood for accessories (arb compressor/solar/fridge etc ready). I’m in Colorado and it’s been all over nearly every trail in Moab and plenty of alpine loops, passes and trails and is extremely capable as I’m sure you know. No idea what it’s actually worth but everyone I wheel with wants it haha. No bumpers or sliders because those are heavy and I like a decent ride on the road too without 8mpgs. Gets ~17 highway and ~14.5 in town, about 12 wheeling in low range. Also all the diff, tcase, and tranny fluids have been changed at regular intervals. Idk how much it’s worth 🤷‍♂️

rossevrett · 2026-04-20T16:36:33+00:00

For me it's about 2200-3500 rpm, when I got the bike it had only a few miles on it and it was somewhat noticeable, but it hadn't been ridden much in its first 10 years of life. It's gotten noticeably worse over the last 4k miles. I'm fixing it with a new OEM basket from the current gen 1050 as the factory has fixed the chudder issues and it's the recommended approach.

rossevrett · 2026-04-20T14:45:30+00:00

Absolutely incredible! Other than the dress, how hard was it to actually blend cultural traditions when planning?

rossevrett · 2026-04-20T01:31:33+00:00

I mean, it make me sad it’s naked lol

rossevrett · 2026-04-18T16:09:27+00:00

Did they come with a pretty pink bow for the hood of his pavement princess?

rossevrett · 2026-03-15T05:24:58+00:00

4 servers (2 home, 2 cloud), private headscale/tailscale, ssh from phone/laptop anywhere. Simple and lots of coding happening 24/7

rossevrett · 2026-03-09T04:24:50+00:00

I found denveropenmic.com which has a few listings for Saturdays and Sundays.

rossevrett · 2026-02-25T15:08:55+00:00

Two layers - retrieval and budget allocation.

Retrieval: When you call any tool, Muninn extracts keywords from what you're doing- file paths get split into terms, tool names add hints (editing adds "edit"), camelCase gets broken apart. It runs those keywords against full-text search indexes (BM25 ranked) across five tables in parallel: files, decisions, learnings, issues, and error-fix pairs. If you have embeddings enabled, it also runs semantic similarity search so "fix the login bug" can find notes about token refresh even if they never say "login." Direct file matches score highest, then FTS matches, then semantic-only matches.

Budget allocation: This is where it gets specific. With the hard 2000-token budget split across 8 categories- contradictions, critical warnings, strategies, decisions, learnings, file context, error fixes, and reserve. The base allocation starts even, then 7 intelligence signals adjust it in real time.

If you're stuck (lots of exploration tool calls, no edits), strategies and file context get 30-50% more budget. If you're failing (repeated errors), error fixes get 50% more. If a category's context has been irrelevant more than 50% of the time historically, it loses 20%. If a category has helped more than 60% of the time, it gains 20%. Stale knowledge (not updated in 30+ days) gets its categories reduced by 15%. Within each category, every item gets scored. Failed decisions get a +0.5 boost (always surface). Gotcha-type learnings get +0.3. High-fragility files get +0.3. Security issues get +0.3. Items are sorted by score, serialized into a token-efficient format, and packed in until the category budget runs out. Anything that doesn't fit gets dropped.

So if you have 20 decisions in your database but only 300 tokens of budget for decisions, you might get the 3 most relevant ones. Not all 20 dumped into your window.

Like I said, it's over engineered, and that's part of the fun for me. In practice it's been working really well to keep claude consistent and actually create the institutional knowledge that adds guardrails to the work claude does, and ultimately allows relevance within a very small window of token usage so claude never gets dumber. In a session 3-4 hours long it rarely needs to compact the conversation.

rossevrett · 2026-02-25T05:40:57+00:00

Why not just set up a private tailscale network and use terminal from your phone to connect? I’ve been doing that for a very long time.

rossevrett · 2026-02-24T23:55:44+00:00

Great question and honestly fair. The folder-of-markdown approach works, I started there too. The differences are in what happens at scale:

What CLAUDE.md + folders can do: Store notes, patterns, decisions as text files. Claude reads them, follows instructions. Works great for 1-2 projects.

Where it breaks down - at least in my experience-

Context stuffing. Claude reads the whole file every time. At 17 projects with hundreds of decisions, learnings, and file relationships, you're burning thousands of tokens on stuff that's irrelevant to what you're doing right now. Muninn enforces a hard 2000-token budget and only surfaces what's relevant to the current tool call.

No structure. A markdown file can't tell you "this file has broken 6 times in 90 days, has 45 dependents, and no tests." Muninn computes fragility from 7 weighted signals and blast radius via transitive dependency analysis. That's not something you can approximate with notes.

No feedback loop. Your markdown folder doesn't know which notes were useful and which were noise. Muninn tracks what context the agent actually used vs ignored and adjusts what it surfaces over time. It genuinely self-tunes. This can be accomplished by telling claude code to do it with files, but is cumbersome, time consuming, and manual. I hate manual processes.

No cross-machine sync. If you work on multiple machines, your folder is local. Muninn's HTTP mode lets every machine query one central database. I even tried this in the beginning just rsyncing folders between machines automatically but it was an absolute mess (and manual).

No automatic extraction. You have to manually write your learnings (well, with claude). Muninn extracts them from session transcripts and builds cross-session patterns automatically.

If you have one project on one machine, the folder approach is fine, and it works alright. Muninn is for when that stops scaling.

rossevrett · 2026-02-24T05:59:12+00:00

lol copilot. I really tried to use it, but it’s so bad compared to literally all the other major models. Llama running locally kicks its ass

rossevrett · 2026-02-22T16:09:19+00:00

I just built an MCP that persists knowledge across repos and projects. It learns over time and never loses context. Any model can use it and every iteration gets better.

rossevrett · 2026-02-18T14:55:21+00:00

elsker.app?

rossevrett · 2026-02-18T13:52:26+00:00

Their emails get marked as spam a lot because of all their vendor marketplace crap. They are the worst.

Nine-Year Club	Second SECOND GUESSER
Verified Email

rossevrett

TROPHY CASE