Project pages and Lab Notes
A Project page is the stable engineering record: what the project is, its current phase, technologies, milestones, media, and public resources. Lab Notes are the chronological record of what happened while the project was being built.
A new Lab Note is appropriate when a meaningful system is built, an experiment produces useful information, a design decision needs to be preserved, a deliberate test produces results, a failure teaches something reusable, or a discovery changes the direction of the work.
Standard note structure
Most notes should answer five questions: Objective — what were we trying to accomplish? Work — what did we do? Result — what happened or works now? Problems or Findings — what failed, surprised us, or was learned? Next — what is the logical next step?
The headings can change when the subject calls for it. A Failure Report may use Problem, Investigation, Cause, Fix, and Lesson; a Technical Note may focus on Architecture or Design Decision. Consistency comes from preserving the engineering story, not forcing every entry into identical headings.
Classification and indexing
Lab Notes use one global chronological sequence: LN-001, LN-002, LN-003, and onward. Project association is stored separately so each project's activity view can automatically collect its own notes.
The supported note classes are Build Log, Experiment, Technical Note, Test Report, Failure Report, and Discovery. Tags should identify the project, major system or technology, and the subject of the note without becoming a second title.
Publishing rule
The notebook should preserve useful checkpoints rather than every individual work session. Notes should be factual, identify what is known versus planned, avoid invented progress, and leave enough context that the work can be understood or resumed later.