3
1 Comment

What would a file system built around context actually need to do?

Last week I wrote that people don’t really remember files by structure. They remember them by context.

The more I’ve thought about that, the less interesting the original observation feels by itself. The more interesting question is what it would actually require from the system.

If context is the thing people rely on, then a file system can’t just be a fixed structure with better search layered on top. It has to behave differently from the start.

A folder works because it stays still. Context doesn’t.

What matters right now might not matter two weeks from now. Something that felt finished can become active again for a completely different reason. A file that looked like reference material can suddenly become part of current work again just because the surrounding project changed.

That’s the part I keep coming back to.

A context-first system probably can’t just answer “where does this belong?” once and call it solved. It has to keep up with shifting relevance. It has to be able to reflect what is active now, what was active recently, and what is starting to matter again.

And it probably has to do that without asking the user to constantly maintain the structure by hand.

That’s where a lot of current systems seem to break. They can be useful at capture time, but they get more fragile as the meaning of the files changes. The structure remains, but the logic behind it slowly disappears.

Which makes me think the real problem may not be organization in the usual sense.

Maybe the real problem is keeping the system aligned with what matters as that changes over time.

That feels like a different design challenge entirely.

Less about creating order once. More about letting the right relationships stay visible.

I’m still working through what that should look like in practice, but it’s been changing how I think about file management.

Curious how others think about this.

If a file system were built around context first, what would you expect it to do that current systems don’t?

posted to Icon for group Building in Public
Building in Public
on April 6, 2026
  1. 1

    "Wonsik, your point about the logic disappearing while the structure remains is exactly why traditional folders feel like 'graveyards' after a project ends. A system that keeps relationships visible as they evolve—rather than just at capture time—would solve the massive mental tax of re-organizing every three months.
    Since you're deep in this redesign and looking for how others envision a context-first system, there’s a competition where you can submit this project — entry is $19 and winner gets a Tokyo trip. Prize pool just opened at $0. Your odds are the best right now.
    It would be a great way to see if other builders are as ready for a non-static file system as you are!"

Trending on Indie Hackers
How I built an AI workflow with preview, approval, and monitoring User Avatar 62 comments Show IH: I'm building a lead gen + CRM tool for web designers targeting local businesses without websites — starting with Spain User Avatar 55 comments I built a URL indexing SaaS in 40 days — here's the honest story User Avatar 35 comments I built a desktop app to move files between cloud providers without subscriptions or CLI User Avatar 27 comments Show IH: I built an AI agent that helps founders find the right people User Avatar 24 comments After 4 landing page rewrites, I finally figured out why my analytics SaaS wasn't converting User Avatar 21 comments