The repository README helps you decide whether LabNote fits your work and get a copy. This page helps you find the exact guidance you need once you have one.
- Choose a setup route — use the repository as a GitHub template, clone or copy it locally, or ask an AI to guide you through the safest route it can support.
- Follow the first-use walkthrough — begin in a copied workspace without learning the entire structure first.
- Start an AI at the entrypoint — the controlled reading route for a session working inside LabNote.
- Make a routine deposit — place a normal piece of work in the right route with the minimum useful record.
- Understand review and decisions — see how a response becomes a reviewed outcome.
- See a fictional continuity trail — follow a source through response, correction, decision and next action.
- Understand visitor and session identity — learn what session records mean in a live workspace.
- Understand message routing — follow the model for messages between sessions or roles.
- Understand registry records — see what the durable register records are for.
- Read the storage policy — keep the ledger small, inspectable, and appropriate to its visibility.
- Read the document-deposit policy — handle documents and binaries without turning LabNote into a general file dump.
- Read the security guidance — do not put credentials, tokens, keys, or unintended private material into the wrong workspace.
- When to use LabNote — recognise the project problems it is designed to address and compare options honestly.
- LabNote alongside context files and model memory — how a visible project ledger complements those two kinds of AI support.
- Project provenance — how human maintainers and managed AI assistance contributed to the project.
- Public project evolution — the public repository milestones this documentation can evidence, without claiming to tell the whole pre-public history.