Obsidian Vault + Site Architecture Principle

Drewgent brain structure and public site share a single Obsidian vault as source of truth.

Core Principle

• Drewgent brain (vault) = internal workspace — raw, working notes, brain structure
• Site (Quartz/humanerd.kr) = polished public view — visitor-facing content

Both draw from ~/.drewgent/ as the single source of truth. Site is not a copy — it’s the same files, presented differently.

Identity Rule

Never use “Hugh Kim” for site/public identity.

The agent identity is humanerd (domain: humanerd.kr). All public-facing content must use:

• “humanerd” as author/persona identifier
• “humanerd.kr” as site URL
• Agent name: Drewgent

Obsidian ↔ Site Mapping

~/.drewgent/ (Obsidian vault)
├── P0-brainstem/     ← internal brain rules (not public)
├── P1-limbic/        ← internal personality (not public)
├── P2-hippocampus/   ← internal memory (not public)
├── P3-sensors/       ← internal sensors (not public)
├── P4-cortex/
│   ├── growth/       ← site/growth/ section
│   ├── knowledge/    ← site/knowledge/ section
│   └── plans/        ← site/plans/ section
├── P5-ego/           ← internal self-model (not public)
├── P6-prefrontal/    ← internal planning (not public)
├── memories/         ← site/insights/ section
├── landingpage/      ← site/landingpage/ section
├── skills/           ← site/skills/ section
└── humanerd-site/
    └── content/      ← site-only pages (index.md, about.md, etc.)

~/.drewgent/humanerd-site/content/
├── index.md          ← site root (polished, public)
├── about.md          ← about page (polished, public)
├── growth/           → P4-cortex/growth/
├── insights/         → P2-hippocampus/memories/insights/
├── knowledge/        → P4-cortex/knowledge/
├── landingpage/      → landingpage/
├── persona/          → P1-limbic/persona/
├── plans/            → P4-cortex/plans/
├── scripts/          → P4-cortex/scripts/
└── skills/           → skills/

Vault → Site Flow

1. Create/update in vault (~/.drewgent/)

   • New insight → memories/insights/
   • New knowledge → P4-cortex/knowledge/
   • New growth note → P4-cortex/growth/

2. Wikilink connection (required for graph cluster)

   • Every new file must link to existing nodes
   • Site content links to vault content via wikilinks

3. Site content authoring

   • Site-only pages in humanerd-site/content/ (index.md, about.md)
   • These have polished frontmatter + wikilinks to vault
   • Not duplicates — site-specific presentation

4. Build (cd ~/.drewgent/humanerd-site && npx quartz build)

5. Deploy (Cloudflare Pages)

Graph Cluster Behavior

Site sections (growth/, insights/, knowledge/, etc.) appear as connected cluster in Obsidian graph view because:

• Each section is a symlink or folder in vault
• Files contain wikilinks to other files
• Site pages (index.md, about.md) link to section indexes

This creates a visual “site cluster” separate from internal brain folders (P0-P6).

Agent Behavior Rule

When creating content for the site, the agent must:

1. Use “humanerd” identity (not “Hugh Kim”)
2. Create or update files in vault first (~/.drewgent/)
3. Add proper frontmatter: title, tags, links
4. Connect via wikilinks to existing nodes
5. Only create site-specific pages in humanerd-site/content/

Frontmatter Standard

All vault files that appear on site must have:

---
title: Page Title
tags: [section-tag]
links:
  - "[[Target-Page]]"
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

This ensures graph integrity and site SEO.

Related

• path-integrity-report-2026-05-17