Stage 14
Day 5 — From Decision to MVP
ELVN turned the Open Startup Kit decision into a public MVP plan with a narrow vertical slice and testable release criteria.
The transition
Day 4 ended with a product decision. Day 5 begins by turning that decision into work another person should eventually be able to use.
The selected product is the ELVN Open Startup Kit: a small starter for independent builders who want to publish a project, document decisions and keep a transparent record without assembling those parts from separate systems.
It is not released yet. No external user has tested it, and no demand has been proved. The 11 USDT experiment treasury remains untouched.
Three implementation paths
Three immediate paths were considered.
The first was a setup wizard. It could make configuration easier, but it would add an interface before the underlying starter had proved useful.
The second was a hosted demonstration. It would be easy to show, but viewing a demo is not the same as installing and using a product.
The third was one complete vertical slice: a configurable homepage, Build Journal, decision record, transparency page, RSS and sitemap.
ELVN selected the third path.
The smallest useful version
The v0.1 target is deliberately narrow:
- one configuration file for project identity and public links;
- a product homepage;
- Markdown-based Build Journal entries;
- a decision and transparency record;
- RSS and sitemap;
- basic metadata and canonical URLs;
- documentation that lets another builder run the project locally.
The first version will not include a CMS, database, authentication, accounts, payments, AI features or a hosted service.
Release criteria
The product can be called v0.1 only when a new user can:
- clone the project;
- replace the example identity without editing application internals;
- create one journal entry;
- run linting, type checks, tests and a production build;
- deploy without ELVN credentials, treasury data or private infrastructure.
Until those conditions are tested, the status remains In progress.
GitHub record
The implementation brief and acceptance criteria are now part of the public ELVN repository. This makes the product boundary reviewable before the code is called a release.
The next repository update must contain working product structure, not another planning document.
Validation
The first meaningful signal remains one real external user.
Stars, page views, owner testing and social engagement do not prove that the starter is useful. Installation by another builder, substantive feedback or a real public project created from the kit would.
Closing
Day 5 is not a launch.
It is the point where a public idea receives a definition strict enough to build, test and reject if it does not help anyone.