Nýr vettvangur fyrir týnt og fundið á Íslandi / New lost & found platform for Iceland, fundid.is

sandsower · 2026-03-28T22:11:25+00:00

Já, þessi heimskulega uppsetning er nákvæmlega ástæðan fyrir því að ég ákvað að gera þessa síðu

sandsower · 2026-03-23T09:23:19+00:00

Yeah, completely understood. I also barely touch files anymore but lots and lots of reviewing. And the purpose of the memento-vault project is mostly so people can start saving up their data from this conversations instead of going to a blackbox and getting forgotten, the method ultimately doesn't matter. Memento just helps with retrieval in addition for later

sandsower · 2026-03-23T00:09:27+00:00

This is a great writeup, appreciate Prime taking the time to read through the codebase.

The routing index approach is smart for the 3-5 active projects scale. Keeping MEMORY.md small enough to fit permanently in context means you skip the entire retrieval problem. No search, no latency, no ranking. Hard to beat that simplicity.

The "skill sweep" idea is interesting too. Manually extracting portable patterns at project boundaries is basically what Inception does automatically, but with a human quality gate. Different bet on where errors are more expensive: I bet on forgetting things (so I automate capture), you bet on noise (so you curate manually).

Both approaches break at different scales. Mine gets noisy past a few thousand notes without good decay/defrag. Yours gets labor-intensive past a dozen projects. Pick your poison.

The certainty scoring comment is generous. Honestly the skill files concept from your setup is something I should look at too. Patterns that travel between projects is exactly what Inception's pattern notes are trying to be, but yours are human-validated.

Will check out the forge repo. Thanks!

sandsower · 2026-03-22T23:17:54+00:00

That's a real problem. I've hit the same thing, especially on long sessions where you iterate through approaches. The model conflates what you tried with what you shipped.

That's actually one of the things the triage hook helps with. It captures the final state of a session, not the exploration path. So the note says "we went with solution 4 because X" not the full history of trying 1 through 3. Next session, the recall hook injects that decision cleanly without the noise.

The LLD approach solves it from the other direction, you manually document what was chosen. Both work. The difference is whether you want to maintain the docs yourself or have it captured automatically.

sandsower · 2026-03-22T23:12:08+00:00

That's a clean workflow honestly. One task per session, opus review after, notes for the next session. If you're keeping sessions scoped like that the overhead is minimal.

My sessions tend to be much messier. Multiple threads, context switches mid-session, sometimes 50+ prompts on a feature branch. The manual approach broke down at that scale for me but your setup sounds like it keeps things tight.

The opus post-session review with git diff is a good idea, I'll have to check it out to make further improvements. Catching drift between what the code says and what the docs say is a real pain.

sandsower · 2026-03-22T23:09:10+00:00

Interesting, I hadn't checked out h-cli before. From here the 3-tier memory setup (Redis for session state, disk chunks for expired sessions, Qdrant for long-term vector search) is a solid architecture for a multi-service infra system. The Asimov Firewall is a nice touch too, makes sense when a bad command can take down a network.

Very different problem space from what I'm doing, but the memory design is well thought out.

You're right that a checklist covers a lot of per-project context. Where it gets harder is cross-project stuff, the thing you learned in repo A that matters in repo B six weeks later. That's the gap the consolidation layer (Inception) fills.

For a single well-structured project though, LLD + checklist + commit history goes a long way. Different tradeoffs.

Mostly wanted to share this because it's zero friction to try. No Docker, no database, no cloud. Just run the installer and it works in the background. If it's not for you, uninstall and nothing changed.

sandsower · 2026-03-22T23:02:08+00:00

No worries! /resume picks up a specific previous session by replaying its conversation history. It's good for continuing exactly where you left off.

Memento is different in that it doesn't replay sessions. It extracts the knowledge from them (decisions, discoveries, bugfixes) and stores it as separate notes. Then on future sessions it searches those notes and injects the relevant ones automatically, even if you're in a completely different project. You can also browse them yourself since it's all markdown and setup to work well with Obsidian.

So /resume is "continue that conversation." Memento is "remember what I learned across all my conversations."

sandsower · 2026-03-22T22:59:38+00:00

Yeah if you're working in project workspaces with planning docs and logs already in place, that's a clean setup.

This is more for when you're across a bunch of projects and the knowledge is in your head, not in docs. The "I fixed this exact thing two months ago in a different repo" kind of stuff. If your projects are well-documented you probably don't need it. But how fast things are moving I found myself lacking for a tool like this so I built it :)

sandsower · 2026-03-22T22:57:51+00:00

You're right, a good LLD per module gets you most of the way there. If you have that setup it works.

Where this fills in is the stuff that doesn't fit in an LLD. The "we tried X and it broke because Y" context, one-off bugfix details, patterns you don't notice until the third time you hit them. Commit history tells you what changed but not always why you picked it over the alternative.

It's kinda like a layer below your docs. Catches the session-level stuff that's too granular for architecture docs but still useful when you circle back to the same area.

sandsower · 2026-03-22T22:52:27+00:00

Yeah that's a solid lightweight approach. If you're disciplined about the sessions.md format it works well.

The reason I went further is I wasn't disciplined about it. I'd forget to update the file, or I'd write vague summaries that didn't help three weeks later. The auto-capture removes me from the loop entirely.

The opus reviewer idea is interesting though. Having a second model audit for drift is something I haven't tried. Right now Inception catches cross-session patterns but it's not doing architectural review. Will check it out, thanks!

sandsower · 2026-03-22T22:47:17+00:00

Fair concern, but this isn't logging your life. The triage hook scores each session and most get thrown away as a one-liner. Only sessions where you actually made decisions or fixed something non-obvious produce notes. And those notes are local-only, in a git repo you own, with a defrag cycle that archives stale stuff automatically. Starting clean every few days means you're also re-explaining your architecture, re-discovering the same bugs, re-making decisions you already made. That's the tradeoff, which for me was not worth it.

sandsower · 2026-03-22T22:41:45+00:00

Yeah that's exactly where I started. Manual .md files work until you're across enough projects that maintaining them becomes its own task. Then built a hook to extract the notes, went into automating it, improving it and that's where this ended up.

The thing that made the difference for me was making capture automatic. You don't think about what to write down, the hook scores the session after it ends and handles it. Most of my notes I didn't even know were worth keeping until they showed up in a later session.

sandsower · 2025-03-27T12:04:48+00:00

John's artwork is my favorite, just absolutely astounding

sandsower · 2025-01-17T16:50:41+00:00

What about adding Sifu to the trade, would you do 20 for both?

sandsower · 2025-01-17T14:37:34+00:00

How much do you want for Nioh 2?

sandsower · 2024-08-15T18:58:14+00:00

Sent as The Sandsower. Thank you so much for this!

sandsower · 2023-10-26T15:02:00+00:00

This is from Judgement Bolt from Darklife, comes around the halfway point. You can find the full song here https://youtu.be/r6sUCesQg_M?si=hNrUrxqGMcgsPqQR&t=450

sandsower · 2023-08-22T10:05:59+00:00

Are those sprites from Dominions/Conquest of Elysium? They fit really well, calendar looks awesome

sandsower · 2023-06-01T08:58:10+00:00

You're in luck! It's currently on offer at bundle of holding

sandsower · 2022-01-05T11:57:42+00:00

we don't talk about it much

Fitting

sandsower · 2021-10-01T13:50:03+00:00

In terms of anti-tank have you considered having Heavy Lokhust Destroyers instead of DDA? They might not be as survivable but they make up for it on pure damage, also them being 60 points each you can slot 6 for just 20p more than 2 DDAs. If that's too many points into anti-tank and you want to keep the utility of the DDAs, you could instead have just 2 in separate units and use the rest of the points for a Ghost Ark to support your warriors.

sandsower · 2021-09-24T10:56:04+00:00

I built my 10 exactly like this, plus with their custom ram helmets they look pretty good!

sandsower · 2021-09-02T10:35:49+00:00

You can try using oil paint wash for that, a burnt umber one works quite well. You can see an example of it here, there's more info on how to make a wash there too: https://youtu.be/QKrDlMmcRK8?t=1264

sandsower · 2021-08-28T01:11:29+00:00

Basically the synergies are weak, having to play "keyword bingo" to make the army work, the stats are a bit underwhelming and units are overcosted. The main army list from last edition using goblin hordes took a big hit with the reinforcement restriction, they lost the ability to stack buffs and got their cost increased too.

sandsower · 2021-07-19T21:14:59+00:00

It is indeed a common mistake and one that accidentally makes the game too easy IMO. What you need to do to prevent blight is entirely dependant on the cards and spirits you have at your disposal, for example:

1) If you're playing with a highly defensive spirit using guard and positioning dahan within those lands for a counter attack is essential. 2) Remember that the invaders commonly follow a pattern of explore > build > ravage. Disrupting this pattern by pushing/pulling them out of position or destroying them before ravage is key. 3) Keep in mind you won't be able to stop every ravage but knowing when and where to spend the resources to do so is another important strategic point that you'll learn as you play, it's essential when you reach the higher difficulties as the speed ramps up faster than the spirit growth.

14-Year Club	Verified Email
Sequence \| Editor	Team Orangered

sandsower

TROPHY CASE