Topic

Why knowledge entrepreneurs should generate their second brain in Google’s Open Knowledge Format (OKF) instead of vault-local WikiLinks — turning a private notebook into discoverable, AI-legible authority infrastructure.

Target Reader

Coaches and knowledge entrepreneurs who already keep a second brain (Obsidian, a wiki, a notes vault) and care about AI citation/visibility, but whose knowledge graph is currently only readable inside their own tool.

The Fear / Frustration / Want / Aspiration

The quiet fear that all the effort poured into a personal knowledge base is trapped — useful to you, invisible to the AI engines that now decide who gets cited. The want: for that same graph to also be an authority signal, without rebuilding it.

Before State

Their vault is wired with [[WikiLinks]]. It interconnects pages internally and that’s the ceiling — a closed system legible only to them and their reader app.

After State

They understand OKF as a portable, standards-based way to express the same graph so other apps and AI scanners can read it — and they set their generator to emit OKF by default, so every future page is born portable at near-zero extra cost.

Narrative Arc

WikiLinks feel like enough — until you realize they stop at your vault’s edge. Google publishes a format meant to be read by everything. The move isn’t to hand-convert; it’s to change what your generator emits, so the private inference engine and the public authority surface become the same artifact.

Core Argument

A second brain expressed in a web-readable standard is worth more than the identical graph locked in a proprietary link syntax — and the cost to choose the standard is trivial if you decide it at generation time, not as a retrofit.

Key Evidence / Examples

Proposed Structure (5–7 beats)

  1. The invisible ceiling of WikiLinks — great inside your vault, mute outside it.
  2. What OKF is and why Google published a knowledge-graph format now.
  3. The reframe: your second brain is both a private inference engine and a public authority surface — same graph, two values.
  4. The cheap decision point: choose the format at generation time, not as a migration.
  5. A concrete experiment: point your wiki generator at OKF, diff against your current output, check internal linking + reader compatibility survive.
  6. When it pays off (GEO/citation-dependent authority) and the honest unknowns.

Editorial Notes

Tone: practitioner-forward, not standards-wonk — the reader cares about being cited, not about spec minutiae. Overlaps with the existing Brief - Get Into the Knowledge Graph Before Your Competitors Do (Wikidata-anchoring angle); keep this one scoped to format portability of your whole graph, not term-level Wikidata linking — they’re complementary, not duplicative. Do not overclaim OKF’s capabilities: Lou himself hasn’t tested the delta yet, so the piece should present the experiment and the strategic logic, not a proven result. Angle to avoid: “Obsidian is dead” — the point is superset compatibility, not replacement.

Next Step

  • Approved for drafting
  • Needs revision
  • Deprioritised