Decomposing information

Break a topic into atomic notes — one idea each — then file each as the unit kind that fits it: concept, entity, fact or process.

Knowledge goes into a wskill as atomic notes: each unit captures exactly one idea, thing, value or task. Before writing anything, break the topic down into these single-idea pieces — if a note tries to hold two ideas, split it. Atomic notes stay easy to link, reuse and keep current, and they are what the templates project into the book and the skill.

Once a piece is atomic, file it as one of the four unit kinds — pick by what it *is*:

• Concept — an idea or mental model: a pattern, a principle, a way of thinking about the topic.
• Entity — a concrete, named thing in the topic's world: a tool, a command, a file type, an organisation.
• Fact — a value, constant or table that can't really be disputed: a default port, an API surface, a lookup table.
• Process — a repeatable task as ordered steps, written for someone who already knows the topic.

When in doubt, run the note through the decision guide — its flowchart and symptom table settle the edge cases (and name the classic mistake: entities are reserved for concrete named things, never a catch-all). Prefer the smaller, more specific kind and link the pieces together with related — the web of links, not a folder hierarchy, is what makes the model navigable.

Each kind is a format with defined fields — structured data. When a topic has a shape the four built-in kinds don't capture, define a new schema for it rather than forcing it into prose.