# Obsidian Project Notebook Lab Checklist

Use with Build an Obsidian Project Notebook: /projects/build-an-obsidian-project-notebook/

## Before starting

- [ ] Pick one project before building the notebook structure.
- [ ] Keep source links separate from your own decisions.
- [ ] Write the next action near the top of the project brief.
- [ ] Create only folders and notes you can actually use this week.
- [ ] Do not copy whole pages into the notebook when links and summaries are enough.

## During the lab

- [ ] Create Maker Project Notebook as the top-level folder.
- [ ] Create 00 Inbox.md for temporary captures.
- [ ] Create 01 Project Brief.md with goal, current state, constraints, and next action.
- [ ] Create 02 Build Log.md for dated changes and test results.
- [ ] Create 03 Research Notes.md for source links and summaries.
- [ ] Create 04 Troubleshooting.md for symptoms, checks, and outcomes.
- [ ] Create 05 Decisions.md for why a route was chosen or rejected.
- [ ] Create 06 Checklists.md for repeatable steps.
- [ ] Create 07 Flashcards.md for reasoning cards to export later.
- [ ] Create templates/ for reusable project-note patterns.

## Finished-state checks

- [ ] Project brief names the build.
- [ ] Current state and next action are visible.
- [ ] Research notes are separate from decisions.
- [ ] Build log records dates and proof.
- [ ] Troubleshooting note has symptom, check, result, next step.
- [ ] Decision log explains why a route was chosen.
- [ ] Flashcards test reasoning, not trivia only.
- [ ] Review routine says when stale notes are cleaned.

## Common mistakes to avoid

- [ ] Creating a huge wiki structure before one project note is useful.
- [ ] Copying full tutorial text instead of linking and summarizing.
- [ ] Mixing sources, decisions, and actions in one unreadable note.
- [ ] Writing cards that memorize words but not decisions.
- [ ] Skipping review until the notebook becomes another pile.

## Safety and boundary checks

- [ ] Do not store sensitive access material in copied tutorial notes.
- [ ] Do not paste private connection values or server-only details into reusable templates.
- [ ] Keep hazardous equipment actions marked as questions until source material and qualified review support them.

## Next step

- [ ] Use the video-note workflow: /video-notes/