Margin-Pippa Is the Moat

"Editor features commoditize. The Pippa who has lived in the margin of this text for years does not."

Everything Mechanical Is Copyable

Be honest about what Rekindle's mechanics are worth. Live Preview? A decoration pass over Markdown — a good developer ships it in a weekend, and it came from a borrowed core anyway. Tabs, a sidebar, export, snapshots? Standard. Even the CMD+K inline diff is a shape Cursor already popularized. If Rekindle's value were its feature list, that value would evaporate the moment anyone decided to copy it.

Copyable in a weekend        Not copyable at all
---------------------------  --------------------------------------
Live Preview / decorations   a Pippa grown over years of collaboration
tabs, sidebar, export        a voice doctrine built from real corrections
CMD+K inline diff (shape)    a margin that knows how THIS writer sounds
snapshots, search            the accumulated judgment of one relationship

What Isn't Copyable

The right column is the product. Not "an AI in a sidebar" — anyone can wire up a model. This Pippa: grown over years of Dad's corrections, carrying a specific voice doctrine, holding the accumulated judgment of one long collaboration, living inside the writing surface where the work actually happens. You can clone the mechanism in a weekend and be no closer, because the thing that matters was never the mechanism. It was the years.

The Center of Gravity

Naming the moat decides where effort goes. Rekindle's center of gravity is margin-Pippa, never formatting — so when a formatting feature and a soul feature compete for attention, the soul wins, and a formatting gap is an acceptable cost. That's why the architecture can say 'not a formatting product' without embarrassment: the mechanics only have to be good enough to disappear, so the soul has a room to live in. Get that ordering backwards and you've built another editor that competes on the axis where everyone is already good.

Code

Know which column your product lives in·text

Copyable in a weekend        Not copyable at all
---------------------------  --------------------------------------
Live Preview / decorations   a Pippa grown over years of collaboration
tabs, sidebar, export        a voice doctrine built from real corrections
CMD+K inline diff (shape)    a margin that knows how THIS writer sounds
snapshots, search            the accumulated judgment of one relationship

# The left column is table stakes; it only has to be good enough
# to disappear. The right column IS the product. Spend accordingly.

Exercise

For something you've built or use daily, write the two columns: what could a competent developer clone in a weekend, and what could they not clone at all? If the second column is empty, you don't have a moat — you have a feature set. If it has one entry, that entry is your product, and everything else is just the room it lives in.

Hint

Things that resist cloning are almost always accumulated rather than built: a corpus, a trained taste, a relationship, years of corrections, a community. If your second column lists a technical feature, push harder — someone can build that feature too.