Skip to content
lemonfiber

The project

lemonfiber is built in the open, and the facts about it live where they are already kept current rather than in a page somebody remembers to update. This section is the way in to those facts: what is finished, what is next, how a version comes together, and the terms the whole thing ships under.

Nothing here is a status report written by hand. The roadmap and the changelog are rendered from the specification’s own version manifests and the implementation status the binary’s repository keeps, at the revisions this site pins — so a figure on either page is a count of marks in a file you can open.

Where the project is

Section titled “Where the project is”
The roadmapEvery version and every milestone, with how much of each one is built.
The changelogWhat each released version delivered, and the requirements it had to prove.
What is builtDeliverable by deliverable: done, in progress, or not started yet.
The version trainHow a release comes together — goals locked first, and a gate that proves they shipped.

What it stands on

Section titled “What it stands on”
The specificationThe requirements lemonfiber is written against, and how to read them.
The licenceHippocratic 3.0 for code, CC BY-SA 4.0 for prose, and what that costs.
The colophonThe nineteen services and the tools this is built on, credited by name.
The FAQThe questions people actually ask, answered canonically and in one place.

Where to go next

Section titled “Where to go next”

If you want to change something rather than read about it, start with cite the spec — the one rule every contribution obeys. If you want to know how the code is put together, start with the repository map. If you have not run it yet, start here.