{"id":1819,"date":"2026-06-11T10:29:45","date_gmt":"2026-06-11T08:29:45","guid":{"rendered":"https:\/\/www.gerjon.com\/?p=1819"},"modified":"2026-06-11T10:29:45","modified_gmt":"2026-06-11T08:29:45","slug":"building-your-ai-second-brain-a-practical-manual","status":"publish","type":"post","link":"https:\/\/www.gerjon.com\/?p=1819","title":{"rendered":"Building Your AI Second Brain: A Practical Manual"},"content":{"rendered":"\n

Every AI conversation you start is a blank slate. You explain your context, your project, your thinking \u2014 again. Then the chat ends and all of it evaporates. The “second brain” solves exactly that problem: it’s a persistent, structured collection of *your*<\/em> thinking that an AI can read, search, and build on. Not the company’s knowledge base. Not a shared wiki. Your brain, externalized.<\/p>\n\n\n\n

On a recent episode of our podcast, Dave Brear walked us through how he built his \u2014 and what surprised me most is that the story doesn’t start with AI at all. you can find the episode here: \u201cIs Your AI Just \u2018Slop\u2019 \u2013 Or a Real Second Brain?<\/a> and you can read the blogpost for a summary of the podcast: AI Second Brain: How We Use Zettelkasten, Obsidian and LLMs to Supercharge Knowledge Work<\/a><\/p>\n\n\n\n

What is a second brain?<\/strong><\/p>\n\n\n\n

It starts with a wooden box in 1950s Germany<\/strong><\/p>\n\n\n\n

The intellectual foundation is the **Zettelkasten**<\/strong> (“slip box”), a method invented by German sociologist Niklas Luhmann. Luhmann wrote his ideas on index cards \u2014 one idea per card, in his own words. These are called **atomic notes**<\/strong>. The magic wasn’t the cards themselves but the *links between them*<\/em>: this idea supports that one, this one contradicts that argument. Over decades, the box became a thinking partner that surfaced connections Luhmann himself had forgotten he’d made.<\/p>\n\n\n\n

The modern recommendation for understanding this philosophy is the book **How to Take Smart Notes**<\/strong> by S\u00f6nke Ahrens. As Dave put it: yes, it could have been a blog post \u2014 but read it anyway.<\/p>\n\n\n\n

Then AI changed the equation<\/strong><\/p>\n\n\n\n

A digital Zettelkasten (Dave uses **Obsidian**<\/strong>) stores everything as plain markdown files, linked with wiki-links, sitting in a local folder you control. Here’s the happy accident: **markdown is the native language of large language models.**<\/strong> Dave never designed his vault for AI ingestion \u2014 but when agentic tools matured enough to work directly with file systems, he pointed Claude at his vault and, in his words, suddenly every conversation started with all the context of everything they’d ever discussed.<\/p>\n\n\n\n

The crucial mindset: expansion, not compression<\/strong><\/p>\n\n\n\n

This is the part most people get wrong. The AI hype machine sells *compression*<\/em>: summarize this document, shorten this email. A second brain is the opposite \u2014 **expansion**<\/strong>. Dave’s best example: a politically sensitive customer email. He fed in over a thousand words of context (stakeholders, politics, motivations, desired outcome) to produce a 300-word email. The AI didn’t think *for*<\/em> him; it challenged his assumptions, stress-tested his framing, and acted as a sparring partner. The ideas were all his. The AI helped him walk the tightrope.<\/p>\n\n\n\n

That’s what a second brain really is: **a thinking system, not a note-taking system.**<\/strong> And one rule remains absolute: human in the loop. Dave is blunt that a significant percentage of first answers from his vault are nonsense. Catching that, correcting it, and arguing back is not a bug \u2014 it’s the exercise that sharpens your own thinking.<\/p>\n\n\n\n

Part 2: How it works under the hood<\/strong><\/p>\n\n\n\n

A working second brain has roughly four layers:<\/p>\n\n\n\n

**1. The vault.**<\/strong> A folder of markdown files. One idea per note, written in your own words, linked together with `[[wiki-links]]`. Tools: Obsidian (most popular), Logseq, or honestly just a folder \u2014 Notepad on Windows can save `.md` files directly.<\/p>\n\n\n\n

**2. Metadata.**<\/strong> Each note carries YAML frontmatter: type (idea, draft, finished article), status, tags, dates. This is what makes the vault *machine-navigable*<\/em> instead of a pile of text.<\/p>\n\n\n\n

**3. Retrieval tooling.**<\/strong> Here’s the problem Dave hit immediately: ask an AI “find all the ideas in my vault” and it has to open and ingest *every single file*<\/em> just to read the headers. He compared it to a snake that swallowed a goat \u2014 too much context, expensive, and degrading. Even million-token context windows don’t give you perfect recall at that scale. The fix is targeted retrieval:<\/p>\n\n\n\n

– A **metadata index**<\/strong>: a small service that pre-indexes all frontmatter, so the AI queries the index instead of opening files<\/p>\n\n\n\n

– **Link traversal**<\/strong>: start from one note and follow the chain of wiki-links \u2014 load a *chain of thought*<\/em>, not a haystack<\/p>\n\n\n\n

– **Semantic search**<\/strong>: find conceptually related notes, including ones you wrote months ago and forgot<\/p>\n\n\n\n

Dave hadn’t written code in 20 years. He didn’t need to \u2014 he described what he wanted and let the AI build the tools. He calls it becoming a product manager of his own cognition.<\/p>\n\n\n\n

**4. The agent.**<\/strong> An AI (Dave’s is a Claude Max subscription he’s nicknamed “Max”) connected to the vault, with standing instructions: *this is our shared space, you can read it and write to it, save what you learn about me, document roadblocks we solve.*<\/em> Fair warning on cost: working this way reportedly uses roughly 10x the tokens of casual chatting. Dave blew past the \u20ac20\/month tier quickly \u2014 and considers it the best money he spends.<\/p>\n\n\n\n

Part 3: Setting it up<\/strong><\/p>\n\n\n\n

Dave’s advice is deliberately anti-prescriptive: don’t download someone’s ten-tool template. Every system that didn’t match how his brain naturally works got abandoned within months. So:<\/p>\n\n\n\n

**Step 1 \u2014 Start with a blank slate.**<\/strong> Create a folder. If you have existing notes to seed it with, great; if not, also fine.<\/p>\n\n\n\n

**Step 2 \u2014 Pick your editor.**<\/strong> Obsidian is the obvious choice: free, local-first, markdown, wiki-links, YAML support. But the storage is just files \u2014 the editor is replaceable.<\/p>\n\n\n\n

**Step 3 \u2014 Point an AI at it and set ground rules.**<\/strong> Tell it explicitly:<\/p>\n\n\n\n

> “This is our shared space. I can write to it; you should feel free to write to it as well. Every time you learn something about me or how I work, save it to a notes area you can read. When we solve a roadblock, document it.”<\/p>\n\n\n\n

**Step 4 \u2014 Let it interview you.**<\/strong> Ask the AI to interview you: who you are, what you do, how you want to work together. Budget about an hour of back-and-forth. This becomes your foundational context.<\/p>\n\n\n\n

**Step 5 \u2014 Do real work in it.**<\/strong> This is the step people skip. The value of a Zettelkasten is not the information it contains \u2014 it’s that you *think inside it*<\/em>. Bring real problems. Develop real deliverables in the vault, not next to it. It compounds: the more you put in, the better it gets, and the gaps you discover (need better search? missing an index?) tell you what to build next.<\/p>\n\n\n\n

**Step 6 \u2014 Keep it firewalled.**<\/strong> Dave puts enormous value on what he calls the sanctity of the vault: he always knows which words are his and which were AI-paraphrased, and he deliberately keeps company data *out*<\/em>. More on why below.<\/p>\n\n\n\n

Want a playground first? Dave published a public subset of his vault at **davebrear.ai**<\/strong> \u2014 you can query it via MCP or fork it from GitHub and point your own agent at it.<\/p>\n\n\n\n

Part 4: Connecting Claude to your vault \u2014 step by step<\/strong><\/p>\n\n\n\n

The connection mechanism is **MCP (Model Context Protocol)**<\/strong> \u2014 the open standard that lets AI assistants talk to external tools and data. There are two main routes: Claude Desktop (chat-style, easiest) and Claude Code (agentic, most powerful \u2014 closest to Dave’s setup).<\/p>\n\n\n\n

<\/p>\n\n\n\n

Route A: Claude Desktop + the filesystem MCP server<\/strong><\/p>\n\n\n\n

**What you need:**<\/strong> Claude Desktop installed, Node.js installed (the filesystem server runs via `npx`), and a vault folder.<\/p>\n\n\n\n

**Step 1 \u2014 Open the config file.**<\/strong> In Claude Desktop, go to **Settings \u2192 Developer \u2192 Edit Config**<\/strong>. This opens (or creates) `claude_desktop_config.json`:<\/p>\n\n\n\n

– Windows: `%APPDATA%\\Claude\\claude_desktop_config.json`<\/p>\n\n\n\n

– macOS: `~\/Library\/Application Support\/Claude\/claude_desktop_config.json`<\/p>\n\n\n\n

**Step 2 \u2014 Add the filesystem server, scoped to your vault only.**<\/strong> Paste this, replacing the path with your actual vault location (Windows paths need double backslashes):<\/p>\n\n\n\n

“`json<\/p>\n\n\n\n

{<\/p>\n\n\n\n

  “mcpServers”: {<\/p>\n\n\n\n

    “second-brain”: {<\/p>\n\n\n\n

      “command”: “npx”,<\/p>\n\n\n\n

      “args”: [<\/p>\n\n\n\n

        “-y”,<\/p>\n\n\n\n

        “@modelcontextprotocol\/server-filesystem”,<\/p>\n\n\n\n

        “C:\\\\Users\\\\gerjon\\\\SecondBrain”<\/p>\n\n\n\n

      ]<\/p>\n\n\n\n

    }<\/p>\n\n\n\n

  }<\/p>\n\n\n\n

}<\/p>\n\n\n\n

“`<\/p>\n\n\n\n

Least privilege applies to AI agents too: point it at the vault folder, not your whole user profile.<\/p>\n\n\n\n

**Step 3 \u2014 Restart Claude Desktop.**<\/strong> Fully quit the app, not just the window \u2014 the config only loads on startup. After restarting you’ll see a tools indicator in the chat input; click it to confirm the filesystem tools (read, write, search, list) are loaded.<\/p>\n\n\n\n

**Step 4 \u2014 Test it.**<\/strong> Ask: *”List the files in my vault and summarize what you find.”*<\/em> Claude will ask your approval before each file operation \u2014 every read and write requires an explicit yes, which keeps you in control.<\/p>\n\n\n\n

**Step 5 \u2014 Set the ground rules.**<\/strong> Create a note in the vault root (e.g. `00-system\/ground-rules.md`) containing your working agreement: this is our shared space, save what you learn about me to `\/about-me`, document solved roadblocks in `\/skills`, atomic notes only, always link. Start each session by telling Claude to read it first. (On claude.ai you can also put these instructions in a Project so they load automatically.)<\/p>\n\n\n\n

**Step 6 \u2014 Run the interview.**<\/strong> *”Read the ground rules, then interview me: who I am, what I do, how I want to work with you. Save what you learn as linked atomic notes.”*<\/em> Budget an hour. This is your foundation layer.<\/p>\n\n\n\n

**Troubleshooting:**<\/strong> if the server doesn’t appear, it’s almost always one of three things \u2014 JSON syntax (a stray comma), a relative instead of absolute path, or an incomplete restart. Logs live in `%APPDATA%\\Claude\\logs` (Windows) or `~\/Library\/Logs\/Claude` (macOS).<\/p>\n\n\n\n

*Alternative without JSON editing:*<\/em> Claude Desktop also supports **Desktop Extensions**<\/strong> \u2014 packaged MCP servers (`.mcpb` files) that install with a click via Settings \u2192 Extensions. Good for community-built Obsidian servers; the JSON route remains the right choice for custom setups.<\/p>\n\n\n\n

Route B: Claude Code in the vault (Dave’s way)<\/strong><\/p>\n\n\n\n

This is the agentic setup: Claude doesn’t just answer questions about your notes, it works *inside*<\/em> the vault \u2014 reading, writing, linking, and building its own tooling.<\/p>\n\n\n\n

**Step 1 \u2014 Install Claude Code**<\/strong> and open a terminal *in your vault folder*<\/em>:<\/p>\n\n\n\n

“`bash<\/p>\n\n\n\n

cd ~\/SecondBrain<\/p>\n\n\n\n

claude<\/p>\n\n\n\n

“`<\/p>\n\n\n\n

**Step 2 \u2014 Create a <\/strong>`CLAUDE.md`<\/strong> in the vault root.**<\/strong> Claude Code automatically reads this file at the start of every session \u2014 it’s where your ground rules become permanent:<\/p>\n\n\n\n

“`markdown<\/p>\n\n\n\n

# Second Brain \u2014 Working Agreement<\/strong><\/p>\n\n\n\n

This vault is our shared thinking space. You may read and write freely.<\/p>\n\n\n\n

## Conventions<\/strong><\/p>\n\n\n\n

– Atomic notes: one idea per file, in my words<\/p>\n\n\n\n

– Every note gets YAML frontmatter: type, status, tags, created<\/p>\n\n\n\n

– Always link new notes to related ones with [[wiki-links]]<\/p>\n\n\n\n

– What you learn about me goes in \/about-me<\/p>\n\n\n\n

– Solved roadblocks get documented in \/skills<\/p>\n\n\n\n

## Behavior<\/strong><\/p>\n\n\n\n

– Challenge my assumptions; don’t just agree<\/p>\n\n\n\n

– When my new thinking contradicts an old note, flag it<\/p>\n\n\n\n

“`<\/p>\n\n\n\n

**Step 3 \u2014 Run the interview**<\/strong> (same as Route A, but now the results persist as files and the instructions persist across every future session).<\/p>\n\n\n\n

**Step 4 \u2014 Build your retrieval tooling.**<\/strong> This is where Dave’s “snake that swallowed a goat” problem gets solved. Once the vault grows past ~100 notes, ask Claude Code to build what Dave built:<\/p>\n\n\n\n

1. A **metadata index**<\/strong>: a script that scans all YAML frontmatter into a single index file, so queries like “show me all open ideas” read one small file instead of ingesting the whole vault<\/p>\n\n\n\n

2. A **link-traversal tool**<\/strong>: give it a starting note and it follows the wiki-link chain, loading a chain of thought instead of a haystack<\/p>\n\n\n\n

3. Optionally, **semantic search**<\/strong> over the vault<\/p>\n\n\n\n

Then describe these tools in `CLAUDE.md` so every future session knows they exist and uses them instead of brute-force reading. Dave hadn’t coded in 20 years \u2014 he described what he wanted and let the AI build it.<\/p>\n\n\n\n

**Step 5 \u2014 Work real problems in it.**<\/strong> Prepare your next presentation, draft your next blog post, think through your next difficult stakeholder conversation \u2014 inside the vault, as linked notes. This is what makes it compound.<\/p>\n\n\n\n

Route C: Query someone else’s brain<\/strong><\/p>\n\n\n\n

Dave and Brian Madden each expose a *public subset*<\/em> of their vault as a remote MCP server \u2014 distinct brains that don’t merge but can talk to each other. On claude.ai, remote MCP servers are added as connectors under Settings (on managed enterprise plans, your admin controls which connectors are allowed \u2014 James hit exactly that wall). Try it with Dave’s public vault at **davebrear.ai**<\/strong>, or build your own read-only vault server as a weekend project \u2014 which conveniently also gives you the endpoint you’ll need for Part 5, Route 3.<\/p>\n\n\n\n

## Part 5: Connecting Microsoft 365 Copilot to your vault \u2014 step by step<\/strong><\/p>\n\n\n\n

One honest disclaimer first: **M365 Copilot cannot read an arbitrary local folder.**<\/strong> Its world is the Microsoft Graph. So every route starts the same way \u2014 getting your markdown somewhere the Graph can see it \u2014 and then differs in how much agent you build on top.<\/p>\n\n\n\n

### Route 1: The 15-minute version \u2014 OneDrive + Agent Builder<\/strong><\/p>\n\n\n\n

The lightweight, no-code route: a declarative agent grounded in your vault.<\/p>\n\n\n\n

**Step 1 \u2014 Sync the vault to OneDrive.**<\/strong> Your vault is just a folder of markdown files; Obsidian doesn’t care where it lives. Move it into (or sync it to) a OneDrive folder, e.g. `OneDrive\/SecondBrain`. If you’d rather not expose everything, sync a curated subset \u2014 remember Dave’s principle of the partitioned vault.<\/p>\n\n\n\n

**Step 2 \u2014 Create a declarative agent.**<\/strong> In M365 Copilot, choose **New agent**<\/strong> (Agent Builder), then **Skip to configure**<\/strong>. Note: this requires an active M365 Copilot license.<\/p>\n\n\n\n

**Step 3 \u2014 Add the vault as knowledge.**<\/strong> On the **Configure**<\/strong> tab, in the **Knowledge**<\/strong> section, use **Browse**<\/strong> to select your OneDrive vault folder (or paste a SharePoint\/OneDrive link).<\/p>\n\n\n\n

**Step 4 \u2014 Write the instructions.**<\/strong> This is where your ground rules go: *”You are my second brain assistant. The knowledge source contains my personal notes as atomic markdown files with YAML frontmatter. Always ground answers in my notes, cite which notes you used, and tell me when my notes contain nothing on the topic rather than inventing an answer.”*<\/em><\/p>\n\n\n\n

**Step 5 \u2014 Test and create.**<\/strong> Ask it: *”What have I written about sovereign cloud?”*<\/em> and verify it cites actual notes.<\/p>\n\n\n\n

**What you get and don’t get:**<\/strong> retrieval and grounding inside the tool you already live in \u2014 but it’s read-only. No writing back, no linking, no tool-building. It’s a window into your brain, not a hand inside it.<\/p>\n\n\n\n

### Route 2: The proper version \u2014 a Copilot Studio agent on SharePoint<\/strong><\/p>\n\n\n\n

More control, better retrieval configuration, shareable with colleagues \u2014 and the natural way to build Dave’s “enterprise layer.”<\/p>\n\n\n\n

**Step 1 \u2014 Put the vault (or its curated subset) in a SharePoint document library.**<\/strong> A dedicated site like `https:\/\/yourtenant.sharepoint.com\/sites\/SecondBrain` keeps permissions clean.<\/p>\n\n\n\n

**Step 2 \u2014 Create the agent**<\/strong> at copilotstudio.microsoft.com: **New agent**<\/strong>, give it a name, description, and instructions (same ground-rules pattern as above, but you have far more instruction room here \u2014 encode your note conventions, your frontmatter schema, and how you want it to behave as a sparring partner, not a yes-machine).<\/p>\n\n\n\n

**Step 3 \u2014 Add SharePoint as a knowledge source.**<\/strong> Go to **Knowledge \u2192 Add knowledge \u2192 SharePoint**<\/strong> and paste the site URL. Write a *detailed description*<\/em> of what this knowledge contains \u2014 the description steers the generative orchestrator’s decision about when to use it, so “Gerjon’s personal knowledge vault: atomic notes on AI strategy, security, governance, and market vision” beats “my notes.”<\/p>\n\n\n\n

**Step 4 \u2014 Check authentication.**<\/strong> The default **Authenticate with Microsoft**<\/strong> setting means queries run on behalf of the signed-in user with their SharePoint permissions \u2014 so colleagues can only retrieve from notes they can already access. Your library permissions *are*<\/em> your vault firewall: get them right before publishing.<\/p>\n\n\n\n

**Step 5 \u2014 Test, then publish**<\/strong> to Teams and M365 Copilot. Now your second brain answers from the same window as your email \u2014 and if you publish a sanitized subset to the team, you’ve built exactly what Dave described: colleagues asking “what does the CTO think about X?” without ever touching your private thinking.<\/p>\n\n\n\n

Route 3: The architect’s version \u2014 MCP into Copilot Studio<\/strong><\/p>\n\n\n\n

This is the pattern that makes your second brain assistant-agnostic: one vault, one protocol, served to both Claude *and*<\/em> Copilot.<\/p>\n\n\n\n

**Step 1 \u2014 Build (or reuse) a vault MCP server.**<\/strong> The same server from Part 4 Route C works, with two requirements: Copilot Studio only supports the **streamable HTTP**<\/strong> transport (SSE is deprecated and no longer supported), and it must be reachable as a hosted endpoint \u2014 Azure Container Apps is a natural home. Keep it read-only to start.<\/p>\n\n\n\n

**Step 2 \u2014 Connect it via the onboarding wizard.**<\/strong> In your Copilot Studio agent, go to **Tools \u2192 Add a tool \u2192 Model Context Protocol**<\/strong>, and either pick an existing MCP connector or register your server with its endpoint URL.<\/p>\n\n\n\n

**Step 3 \u2014 Configure authentication.**<\/strong> The wizard supports OAuth 2.0, including **dynamic discovery**<\/strong> (Dynamic Client Registration) if your server supports it \u2014 the cleanest option. Entra ID-backed per-user auth means the vault server knows *who*<\/em> is asking, which is what makes a multi-user “query the team’s brains” scenario governable.<\/p>\n\n\n\n

**Step 4 \u2014 Add the server’s tools to the agent.**<\/strong> After connecting, choose **Add to agent**<\/strong> (or **Add and configure**<\/strong>); the server’s tools \u2014 your metadata index query, your link traversal, your semantic search \u2014 now appear on the agent’s Tools tab for the orchestrator to call.<\/p>\n\n\n\n

**Step 5 \u2014 Test the difference.**<\/strong> Knowledge sources give you RAG: “find passages about X.” MCP tools give you *operations*<\/em>: “traverse the link chain from my sovereign-cloud note and summarize the argument I’ve been building.” That’s the difference between searching a brain and thinking with one.<\/p>\n\n\n\n

**The honest comparison:**<\/strong> today, Claude \u2014 especially Claude Code \u2014 is meaningfully better at the *agentic*<\/em> second-brain workflow: reading, writing, linking, and building tooling inside your vault. Copilot is better at meeting you inside the enterprise walled garden, with identity, permissions, and governance already handled. They’re not competing patterns; they’re the personal layer and the corporate layer of the same idea \u2014 and Route 3 is the bridge between them.<\/p>\n\n\n\n

Part 6: The uncomfortable governance questions<\/strong><\/p>\n\n\n\n

Three points from the episode that every IT leader should sit with:<\/p>\n\n\n\n

**This is not a DLP problem \u2014 and that’s the problem.**<\/strong> Dave’s vault contains zero company files, zero customer data, no clipboard copies. Only his own observations. Yet ask it about “super secret initiative X” and it can synthesize something scarily close to reality. Traditional data loss prevention has nothing to detect, because nothing was ever copied.<\/p>\n\n\n\n

**Shadow second brains are coming.**<\/strong> People who work this way don’t go back. If the enterprise doesn’t offer a sanctioned way to do this inside the walled garden, people will do it anyway \u2014 personal subscription, personal device, personal file share \u2014 and you will have no visibility whatsoever. Dave’s prediction: this goes from a niche practice to a significant factor fast. The only winning move is to provide the capability *inside*<\/em> governance, not to ban it.<\/p>\n\n\n\n

**Who owns your cognition?**<\/strong> James raised the sharpest question: if your employer hosts a system that captures how you think, what stops them from keeping 80% of your value at 0% of your salary after you leave? Dave’s tentative answer \u2014 a personal encryption layer over the “this is me” tier of context, useless without you in the loop \u2014 doesn’t exist as a product today. But he sketched a layered model worth remembering: company context at the base, role context above it, and *you*<\/em> at the top. The top layer should be portable and yours.<\/p>\n\n\n\n

Where to start, in one paragraph<\/strong><\/p>\n\n\n\n

Create a folder. Open it in Obsidian. Point Claude (Desktop or Code) at it, set the ground rules, and let it interview you for an hour. Then bring it one real problem this week and work the problem *inside*<\/em> the vault. Read *How to Take Smart Notes*<\/em> when you want the philosophy. And if you want to try before you build: Dave’s public vault is at davebrear.ai.<\/p>\n\n\n\n

The tech, as always, is the easy part. The discipline of thinking in atomic notes, in your own words, every day \u2014 that’s the system. The AI just makes it compound.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Every AI conversation you start is a blank slate. You explain your context, your project, your thinking \u2014 again. Then the chat ends and all of it evaporates. The “second brain” solves exactly that problem: …<\/p>\n","protected":false},"author":1,"featured_media":1821,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[32,11],"tags":[],"class_list":["post-1819","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai","category-microsoft"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.gerjon.com\/wp-content\/uploads\/2026\/06\/zettelkasten.png?fit=1188%2C625&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p59CpB-tl","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/1819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1819"}],"version-history":[{"count":1,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/1819\/revisions"}],"predecessor-version":[{"id":1820,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/1819\/revisions\/1820"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/media\/1821"}],"wp:attachment":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}