The problem

Writers and worldbuilders have always had a tool problem.

Not a lack of tools. The opposite. There are dozens of apps that claim to be built for writing. Some are powerful. Some are beautiful. Most are neither. And almost none of them understand that writing a novel and building the world that surrounds it are two sides of the same act, not two separate workflows.

So you end up piecing things together. Scrivener for the manuscript, Notion for the lore, a notes app for the scraps that do not fit anywhere yet. It works, kind of. But it is fragmented, and fragmentation is the enemy of the mental state that good writing actually requires.

I have been that writer. Jumping between apps, losing context, rebuilding the same structures over and over in tools that were never really designed for what I needed them to do. At some point I stopped looking for the right tool and started thinking about what it would actually take to build it.

That is where Palimpsest comes from.

What Palimpsest is

Palimpsest is a writing environment for writers and worldbuilders who take their work seriously.

Not a notes app. Not a project manager with a text editor bolted on. A space designed from the ground up around one idea: your writing deserves its own world, and that world should feel like yours.

Calm. Focused. Everything in one place, nothing in the way. Your manuscript, your characters, your lore, your fragments. All of it living together, the way it actually lives in your head when a story is working.

The name says something about the intention. A palimpsest is a manuscript where old writing was scraped away to make room for new writing, but traces of what came before remain visible beneath the surface. That tension between layers, between drafts, between versions of a story, is exactly what this application is built to hold.

It is not finished. It is not even close to finished. But the vision is clear, and that clarity is what this post is about.

Why it won't die

This is the part I want you to actually hear.

Every writer who has ever invested time into a tool knows the fear. You build your workflow around it, you trust it with your work, and then one day the updates stop. The founder moves on. The company pivots. The app quietly becomes abandonware. And you are left migrating years of work into something new, again.

I am not going to promise you that will not happen with Palimpsest. Promises are easy.

What I will tell you is this: I am a writer. I am building Palimpsest because I need it. Not because I saw a market gap, not because someone told me it was a good business idea. Because I sit down to write and I feel the same frustration you feel, every single time. This application is, before anything else, mine.

That changes the dynamic entirely. I am not building a tool for a user I am imagining. I am building a tool for myself, and inviting you along. Which means the day I stop caring about Palimpsest is the day I stop writing. I will let you decide how likely that is.

Where things stand

Honest answer: early. Very early.

The core editor is being built. The vision for how manuscripts, worldbuilding, and notes coexist inside the application is clear and being translated into actual software. Some things work. A lot of things do not yet.

I am not going to show you screenshots of half-finished interfaces and pretend they represent something ready. What I can tell you is that the foundation is serious, the architecture decisions have been made carefully, and nothing here is being rushed toward a launch date that does not exist yet.

This is a build-in-public project. That means you get the real version, not the polished marketing version. The messy middle, the pivots, the moments where something finally clicks. All of it.

If that sounds like something you want to follow, you are in the right place.

What comes next

First, follow along. This is the first post of many. The build will be documented here, honestly, at whatever pace the work actually moves. No artificial hype, no vanity updates.

If you want to be closer to the process, the Discord is coming. It will be the place where I share things before they are ready to be written about. Early previews, questions, decisions I am not sure about yet. If that interests you, keep an eye out.

And if you are a writer or a worldbuilder who feels that frustration I described in section one, I would genuinely love to hear about your setup. What you use, what drives you crazy about it, what you wish existed. That conversation matters more to me right now than any feature I could ship.

Palimpsest is early. But it is real, it is moving, and it is being built by someone who needs it just as much as you do.

Welcome.