Folder structure (numbers = muscle memory)
00 System runs the machine · 01 Templates note blueprints · 02 References core manuals · 03 Agencies FL jurisdictions · 04–17 knowledge domains · 20 Projects real work · 21 Daily logs · 22 Inbox capture.
Folders are coarse buckets; links and tags do the real organizing. When unsure where a note goes, put it anywhere and link it from the right MOC — findability comes from links, not filing.
Note naming convention
- Plain descriptive titles, no dates in titles:
Crash Rate Calculation, not2026-07-crash-rate. - Prefixes that sort and signal:
T -templates ·MOC -maps of content ·Workflow -step-by-step procedures ·PRJ -projects (e.g.,PRJ - Corridor Safety Study). - Daily notes:
YYYY-MM-DD(automatic). - Agency notes: exact agency name (
Hillsborough County,FDOT District 7). - One idea per note. If a note needs a table of contents, split it.
Tagging system (three axes, keep it small)
- Type:
#type/reference#type/concept#type/workflow#type/project#type/lesson#type/source#type/template#type/checklist - Domain:
#domain/safety#domain/calming#domain/parking#domain/signals#domain/tia#domain/design#domain/cad#domain/software#domain/code#domain/data#domain/pm#domain/career#domain/life - Status:
#status/verify(unconfirmed — check before real use) ·#status/verified·#status/learning·#status/ask-pe - Source class (C.1–7):
#src/official#src/professional#src/tutorial#src/example#src/community#src/code#src/opinion
Rule: ≤4 tags per note. If you invent a new tag twice, add it here; otherwise delete it.
Linking philosophy
- Link liberally while writing — write a link to
Turn Lane Lengtheven if the note doesn’t exist yet. Unresolved links are your future study list (see graph view → orphans). - Every project note links to the references and workflows it used → over time your references accumulate real project context.
- MOC notes are curated tables of contents per domain; update them during weekly review, not in the moment.
See also: QAQC System · Lessons Learned System · Weekly Review Routine