Skip to content
lemonfiber

The specification

The specification is the canonical description of lemonfiber: what it must do, how the system is assembled, and the rules a change is held to. Code cites it. Pull requests cite it. Nothing lands anywhere in the project without naming an identifier that already exists in it.

It is written and checked in the spec repository, and read here. Every page below is that repository’s own file at the revision this site pins, and each one says at its foot which revision that was.

Where to start

Section titled “Where to start”
VisionThe problem, and the principles every later decision is measured against.
How the specification worksIdentifiers, statuses, the release train and the change lifecycle.
GlossaryThe words this project uses, and what each one means here.
Feature boardEvery feature, its area, its track and its status.

The nine sections

Section titled “The nine sections”
Overview and decisionsVision, roadmap, glossary, and the sixteen architecture decision records.
FunctionalSeventy-three features and nine end-to-end journeys.
ArchitectureHow the system is assembled, and the seven normative contracts between its parts.
RepositoriesOne page per repository: what it is for, and the rules specific to it.
QualityThe bar a change is held to — testing, coverage, comments, CI and security.
GovernanceHow change enters: the canonical-spec rule, RFCs, sign-off, issue routing.
BrandThe visual language as requirements, and the contrast contract.
OperationsReleasing, the version train, maintainers and one-time setup.
AppendixThe FAQ, the colophon, and why the licence is what it is.

If you were looking for something else

Section titled “If you were looking for something else”

The specification says what must be true. It is not a guide to using the tool.