"Roughly 80% of Vesta is inherited from Waystone. The design energy went into the one thing that actually differs."
What 'Seeded From' Actually Means
Vesta was seeded from Waystone at roughly eighty percent reuse — and it's worth being precise about what that phrase does and does not mean. It does not mean Vesta is a copy of Waystone with the name changed. It does not mean Vesta imports Waystone's code at runtime, and it does not mean the two share a database. Seeding is inheriting the shape: taking Waystone's proven, field-hardened contracts — the crumb model, the local-first capture contract, the composer trio, the consultation assembly — and rebuilding a journal from that spirit. What crosses over is the shape of the solution, not the bytes.
This is the difference between a remaster and a remake. A remaster keeps the old content and improves the texture — that's the migration mindset, converting old data into a new coat of paint. A remake rebuilds from the spirit of the original using current ground truth, current voice, the better schema, in one pass. Vesta is a remake of Waystone's shape pointed at a new domain: same battle-tested contracts, freshly built for a journal instead of a trip.
Why Inherit at All?
The reason to start from a sibling's shape instead of a blank page is that the eighty percent is already hardened. Waystone's capture contract, offline outbox, and two-truth rules weren't designed in the abstract — they carry field bruises from a real trip through Switzerland. Rebuilding them from scratch would mean rediscovering every one of those bruises the hard way. By inheriting the shape, Vesta starts on the far side of all that learning and spends its entire design budget on the twenty percent that's genuinely new: the open timeline. That's the reuse ledger in action — adopt what's proven, adapt the shape where the domain differs, and invent only the true delta.
The Delta Is Where the Effort Goes
Because the shape is inherited, you can see exactly where Vesta's real work is. The crumb, the outbox, the composer, the assembly consultation — all adopted, all working on day one. The open timeline, the two date truths pointed at a journal, the categorical shelf, the multi-year layer — that's the invented delta, the part that makes Vesta a journal rather than a trip planner. A child app done well should look mostly like its parent, with a small, sharp region of genuine difference. If your 'new app' shares almost nothing with the sibling it was seeded from, either it wasn't really seeded, or you reinvented eighty percent you could have inherited.