knowledge-architecture

Organize by asking what each thing essentially is rather than where it should be filed. Classify entities as substances (projects, people, tools), properties (states, qualities), or events (actions, milestones), then group by essential properties and tag by accidental ones.

Essential properties define what makes a thing that thing, such as a portfolio site displaying work and representing identity. Accidental properties like the framework or hosting platform could change without altering identity, so they belong in tags rather than folder structure.

Use typed links such as depends-on, extends, contradicts, and exemplifies instead of generic links. The Skill provides wikilink patterns with typed syntax and recommends maintaining explicit relation maps so connections stay navigable and bidirectional.

The recommended hybrid structure separates entities, relations, views, contexts, and meta documentation into distinct folders. This avoids deep nesting decisions while keeping cross-type entities accessible through indices rather than hierarchy.

Avoid over-classification when starting out, since too many categories create friction. Start simple with a few entity types and relations, then refine the ontology as real usage patterns emerge from your notes.