Personal Knowledge refers to the individual methods, systems, and digital gardens humans use to store, organize, and build upon their memories and information streams.

Modern efforts utilize digital systems like Obsidian or semantic architectures to form a Second Brain.

Why semantics elevate your 2nd brain

Typed links over simple backlinks

Instead of a simple un-typed link from Gregory's page to Bella's page, semantic PKM defines the exact nature of the relationship:

# Inside Gregory.md
owns: Bella

This is parsed as a typed graph triple (wiki:gregory wiki:owns wiki:bella), allowing the graph to mathematically reason about family, colleague, or friend connections.

Built-in structural correctness

Traditional notes suffer from "schema drift" where you forget to add fields like dates or tags. The Wiki CLI uses SHACL shapes and optional JSON Schema bindings (wazoo:jsonSchema) to audit your notes automatically. This ensures your second brain remains consistently structured and complete.

Infinite dynamic synthesis (SPARQL)

Instead of manually maintaining index lists or tag pages, you write a simple SPARQL query. When you run wiki render, the CLI automatically updates your indexes, dashboards, and maps dynamically!

Declarative vs. procedural knowledge representation

A modern second brain must distinguish between declarative knowledge ("knowing what") and procedural knowledge ("knowing how"):

• Declarative Knowledge: Represented statically as semantic facts, class hierarchies, and properties within your markdown frontmatter. These are parsed into the permanent RDF graph.
• Procedural Knowledge: Represented dynamically as executable actions, workflows, query parameters, and validation rules (e.g., active SHACL shape rules, JSON Schema bindings, and custom SPARQL blocks). The CLI automates this procedural layer through commands like wiki check and wiki render, transforming static notes into an active, self-correcting system.