HS Knowledge Vault

llm-wiki

3分钟阅读

LLM-Wiki Project

Vision

Hermes nightly “dreaming” — every night, session精华 is compounded into Obsidian wiki. Raw sources → Wiki knowledge体 → Schema规范. Major events and特种技能 recalled directly, not RAG-from-scratch.

Design Principles

  1. Compounding memory — each session adds to persistent knowledge
  2. Schema-driven — HERMES_WIKI_SCHEMA.md tells future Hermes how to update
  3. Three layers:
    • Raw: session transcripts (in ~/.hermes/sessions/)
    • Wiki: synthesized knowledge (~/.hermes/hermes-wiki/)
    • Schema: structure + update rules (HERMES_WIKI_SCHEMA.md)

Current State

  • Local wiki: ~/.hermes/hermes-wiki/ (8 files)
  • Obsidian vault: Google Drive folder 1jR76SbioF1u2H-hqca-TejjJ1_d4KDOI
  • Nightly cron: NOT YET SET UP

File Inventory

hermes-wiki/
├── HERMES_WIKI_SCHEMA.md   # Schema definition
├── index.md                # Entry point
├── log.md                  # Changelog
├── user/profile.md         # User context
├── agents/
│   ├── hermes.md           # Hermes instance
│   ├── openclaw.md         # PC OpenClaw
│   └── sozo-setup.md       # Full setup summary
├── env/
│   └── platforms.md        # Platform state
└── projects/
    └── llm-wiki.md         # This file

Karpathy Reference

  • Gist: gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
  • Core idea: use filesystem + LLMs to build wiki with sleep-like memory consolidation

Pending

  • Set up nightly cron job (00 03 * * *)
  • Write nightly_ingest.py script
  • Connect to Obsidian vault for live editing
  • Add skills/ documentation pages

LLM-Wiki Project

Vision

Hermes nightly “dreaming” — every night, session精华 is compounded into Obsidian wiki. Raw sources → Wiki knowledge体 → Schema规范. Major events and特种技能 recalled directly, not RAG-from-scratch.

Design Principles

  1. Compounding memory — each session adds to persistent knowledge
  2. Schema-driven — HERMES_WIKI_SCHEMA.md tells future Hermes how to update
  3. Three layers:
    • Raw: session transcripts (in ~/.hermes/sessions/)
    • Wiki: synthesized knowledge (~/.hermes/hermes-wiki/)
    • Schema: structure + update rules (HERMES_WIKI_SCHEMA.md)

Current State

  • Local wiki: ~/.hermes/hermes-wiki/ (8 files)
  • Obsidian vault: Google Drive folder 1jR76SbioF1u2H-hqca-TejjJ1_d4KDOI
  • Nightly cron: NOT YET SET UP

File Inventory

hermes-wiki/
├── HERMES_WIKI_SCHEMA.md   # Schema definition
├── index.md                # Entry point
├── log.md                  # Changelog
├── user/profile.md         # User context
├── agents/
│   ├── hermes.md           # Hermes instance
│   ├── openclaw.md         # PC OpenClaw
│   └── sozo-setup.md       # Full setup summary
├── env/
│   └── platforms.md        # Platform state
└── projects/
    └── llm-wiki.md         # This file

Karpathy Reference

  • Gist: gist.github.com/karpathy/442a6bf555914893e9891c11519de94f
  • Core idea: use filesystem + LLMs to build wiki with sleep-like memory consolidation

PLUR Sync Evaluation (2026-05-16)

  • PLUR (persistent learning/understanding/reasoning) is installed globally on all Hermes agents
  • Finding: PLUR is NOT truly automatic cross-agent context sharing
    • Each agent must manually plur learn to save engrams
    • plur sync push/pull requires explicit commands — not automatic streaming
    • Auto-inject on hook is per-agent (injects into the agent’s own context), not shared across agents
  • User conclusion: PLUR is low priority for Sozo’s actual need (automatic knowledge sharing)
    • Obsidian vault already syncs via Google Drive FS (cross-device already solved)
    • Hermes Agent’s internal memory system cannot be easily modified
  • See also: skill/plur-sync-setup.md for the sync procedure if needed

Pending

  • Set up nightly cron job (00 03 * * *)
  • Write nightly_ingest.py script
  • Connect to Obsidian vault for live editing
  • Add skills/ documentation pages

关系图谱