Changing lemonfiber
This site is for changing lemonfiber: how a change gets in, how each repository is built, and how the core is put together. Running lemonfiber, or building on its API, is on the documentation site.
Every page here belongs to the repository that holds what it describes, and says at its foot which revision it was rendered from.
The one rule
Section titled “The one rule”Every change cites a requirement in the
specification, and that requirement
already exists. A pull request whose Spec: line names an identifier the
specification does not hold is closed by spec-check. The rules a change
follows are specification pages:
- Contributing: the rule, finding the identifier to cite, and what a commit message carries
- Working in the repositories: claiming work, commits, opening and owning a pull request
- Working with AI agents: the five rules an agent keeps, and what it reads first
- The RFC process: how a change the specification does not hold yet is proposed
- Where an issue goes: which repository a report belongs in
Taking partThe organisation's contributor guide, its code of conduct, where to ask, and how to report a vulnerability.
The repositoriesEach repository's own front door: what it is, and how to build and test it.
How the core is builtThe architecture notes to read before touching the Rust workspace.
The brandColour, type and the marks, and the rules for using them.