Working agreement
How knowledge arrives in the handbook.
New knowledge
There is no automation (yet) for new knowledge arriving here. Also, there is no single rule set in stone how it arrives to the handbook.
However, below are a few reasons why one might want to document a finding:
- Speed up onboarding for new team members
- Preserve common domain knowledge (so it is not lost when people leave or forget)
- Create consistency (so different employees follow the same process)
- Avoid repeating mistakes
- Reduce repeated questions
- Improve decision-making
- Support growth (because informal knowledge does not scale well)
- Clarify responsibilities and expected standards
- Meet legal, security, or compliance requirements
- Make improvement easier (because a documented process can be reviewed and changed)
Existing knowledge revisited (reverse-engineering)
To this date (08/2026), the project has introduced a lot of machine-generated code and documentation. The code is not always self-explanatory, and generated /docs are hard to inspect and always rely on. Some of these docs are conflicting and need verification.
Part of the handbook work is to verify existing knowledge, and to distill the findings. This is a reverse-engineering process that requires human supervision.
Linear tracks this work under the following initiatives:
How to add
Simply open a Pull Request with a new page or an edit to an existing page within the apps/handbook directory.
Make sure to include a description of the change, and link to any supporting evidence or discussion.
Once it is approved and merged, the new knowledge will be redeployed and available to all contributors.