Why I Started ProseForge

ProseForge didn’t start as a startup idea.

It started as a problem I kept running into while trying to write.

I was exploring story ideas that touched on bigger themes—time as a constant, multiple timelines, creator/caretaker roles, memory, identity—and I kept running into the same issue: I could generate ideas fast, but I couldn’t reliably keep them together.

A good concept would come out in one chat.
A character detail would show up somewhere else.
A strong scene would exist in a draft, but not match the version of the character I had in my head anymore.
An image would look great once, then drift the next time I tried to generate the same character.

It wasn’t just “writing.”
It was continuity, versioning, worldbuilding, character consistency, revision history, and trying not to lose the thread.

At some point I realized I wasn’t just writing stories—I was investigating tooling.

And that’s where ProseForge began.

The real problem I was trying to solve

A lot of writing tools are great at one thing:

• drafting text;
• taking notes;
• formatting;
• publishing;
• or generating AI output.

But my workflow kept crossing all of those boundaries.

I needed a way to:

• capture ideas quickly;
• preserve continuity across versions;
• track changes without losing earlier directions;
• experiment with different creative paths;
• generate assets (text and images);
• and keep everything organized enough that I could come back later and continue.

The more I worked on stories, the more obvious it became that I needed something that treated creative work more like a living system than a pile of documents.

That pushed me toward building a toolset instead of relying on a single app.

The tooling investigation that turned into a platform

A big part of ProseForge came from hands-on experimentation.

I started trying to piece together a workflow from existing tools and services:

• repos for versioning and organization (including Bitbucket);
• structured storage for drafts and metadata;
• pipelines for generating and iterating on text;
• image generation workflows for character and scene exploration;
• PDF authoring/export paths for readable, shareable outputs;
• and eventually broader publishing and production concerns.

Some of this worked.
Some of it was clunky.
Some of it worked once but broke flow the moment I needed consistency.

That investigation was incredibly useful, because it made one thing clear:

the problem wasn’t just “how do I generate content?”
It was:
how do I build a repeatable creative process that supports iteration without losing continuity?

That’s a very different problem.

And once I started framing it that way, ProseForge stopped looking like a simple writing app and started looking like a creative operating system.

Continuity matters more than people think

One of the biggest pain points for me was continuity.

Not just plot continuity—though that matters too—but continuity of:

• character voice;
• visual identity;
• world rules;
• emotional arc;
• and the reason a story exists in the first place.

When you’re exploring multiple versions of a story (or multiple stories in the same universe), it’s very easy to lose strong ideas in chats, screenshots, random notes, and half-finished drafts.

That gets worse when AI is involved, because generation is fast, but consistency is not automatic.

You can get amazing outputs.
You can also get drift.

So a lot of what ProseForge is trying to do is reduce that drift:

• preserve what matters;
• make iteration easier;
• and help creative work stay coherent as it grows.

Why I didn’t just keep using existing tools

I tried.
And I still use a lot of them.

This isn’t really a “everything else is bad” story.

It’s more that my workflow became a combination of:

• writing;
• engineering;
• experimentation;
• asset generation;
• revision control;
• and production planning.

Once you’re living in that overlap, the seams between tools become the problem.

You start spending too much energy on:

• where things are stored;
• which version is current;
• how to reproduce a good result;
• what changed;
• and how to move from idea → draft → revision → output without rebuilding the process every time.

ProseForge is my answer to that.

It’s the system I wanted while I was in the middle of all of that.

What ProseForge is for (at least for me)

At its core, ProseForge is about helping me—and eventually other writers/builders—do creative work without losing momentum or structure.

It’s for:

• messy ideation;
• structured development;
• continuity across drafts;
• character/world tracking;
• AI-assisted experimentation;
• and turning scattered creative output into something I can actually build on.

I’m building it for the kind of process where stories evolve, branches happen, ideas come back later, and the tooling needs to support that instead of fighting it.

Why now

Because I got tired of losing good ideas.

And because I’ve spent enough time in software, systems, and performance work to know that if a workflow keeps breaking in the same place, it’s usually not just a discipline problem—it’s a tooling problem.

So I started building the thing I wanted to use.

That’s ProseForge.

It started as a way to support my own writing process.
It’s becoming a toolset for creative continuity, iteration, and output.

And honestly, I’m still building it the same way it started:
one problem at a time, one workflow at a time, one story at a time.