I've been interested in starting to document how my use of a knowledge graph to organize my notation system evolves over time, so here is a beginning template of what that looks like, and we will see how it evolves year to year.

Fragments  →  Logs  →  Journals  →  Research  →  Projects  →  Systems

• Fragments feed Logs: raw material becomes documentation of doing.
• Logs feed Journals: reflections arise from repeated actions or patterns.
• Journals feed Research: sustained curiosity builds structured inquiry.
• Research feeds Projects: findings evolve into things you make.
• Projects feed Systems: successful patterns become reusable templates.

Level	Name	Density	Primary Function	Example Sources	Children / Inputs
0	Fragments	🔹 Lightest	Capture small sparks of information — quotes, links, screenshots, single thoughts, or observations.	Web snippets, books, podcasts, conversations.	None (atomic)
1	Logs	🔹 Low-medium	Track your own activity or process. Documentation of builds, configs, debugging, studio notes, etc.	“Got Postgres vector search working,” “Cursor prompt rules.”	Fragments
2	Journals	🔸 Medium-high	Reflective or integrative writing — lessons, patterns, emotional or conceptual synthesis over time.	“What I learned debugging async state,” “Why I keep building climate tools.”	Fragments, Logs
3	Studies	🔸 High	Structured exploration of a question or domain. Usually aims toward generalizable understanding or reusable insight.	“LLM data pipelines for environmental sensors.”	Journals, Logs, Fragments
4	Projects / Works (rename suggestion below)	🔸 Highest	Outcome-oriented, has a start and end. Produces artifacts, code, or deliverables.	“Flex digital twin MVP,” “Home-screen history generator.”	Research, Journals, Logs
5	Systems / Frameworks (optional meta-layer)	🔸 Meta-level	Abstractions that describe how you work — templates, taxonomies, SOPs, prompt frameworks, etc.	“How to structure a research doc,” “Naming taxonomy for knowledge types.”	Everything beneath it