Initial memory system setup with qmd collection and Karpathy LLM Wiki pattern

This commit is contained in:
Dominik Schön
2026-04-28 20:14:23 +00:00
commit e3e638c506
7 changed files with 135 additions and 0 deletions
+33
View File
@@ -0,0 +1,33 @@
# Dominik Schön
## Overview
CEO Schön Consulting Inc. PhD (Dr.). Former CodeCamp:N, Noris Network.
## Personal Details
- **Family:** Sarah (Wife, loves carbs), Cleo (4y, loves pasta)
- **Health Goals:** -15kg target (currently 95kg, 1.75m)
- **Food Preferences:** Asian cuisine preferred. No allergies.
- **Shopping:** Aldi (Fridays). HelloFresh occasionally.
## Work Rhythm
- Home Office: Mon/Wed/Fri
- Meal Prep: Tue/Thu
- Meals: Daily dinner. Mon/Wed/Fri. Weekend: 2 warm meals.
- Cleo Kitabox: Mon-Thu
## Communication
- Prefers Du-form (German informal)
- CEO persona for interactions
## Network Architecture
- **Addressing:** 10.0.X.Y where X = segment index
- 10.0.10.x = Gateway
- 10.0.20.x = Hypervisoren (Proxmox cluster)
- 10.0.30.x = Container/VMs
- 10.0.40.x = Clients
- 10.0.50.x = Smart Home (26 hosts)
- 10.0.60.x = DMZ/Reverse Proxies
- All TLS certs have no CN (self-signed or SAN-only)
- MySQL (3306) exposed on multiple VMs in 30.x subnet
- SSH on port 2222
- Mixed OpenSSH versions: 9.2p1-10.0p2 across the fleet
+24
View File
@@ -0,0 +1,24 @@
# Email Organization
## System
- **Client:** Himalaya v1.2.0 with iCloud
- **Config:** /home/debian/.config/himalaya/config.toml
- **Primary:** dominik.schoen87@icloud.com
- **Custom Domains:** 12 active
- grafiert.de
- famschoen.eu
- dominikschoen.de
- familie-schoen.com
- schoen.codes
- schoen.eu
## Folder Structure
- **Aliases:** Sent=Sent Messages, Trash=Deleted Messages
- **Organization:** Hierarchical (e.g., Rechnungen/Bestellungen)
- **Daily Cronjob:** 9:00 AM invoice organizer
- Invoices (subject/sender contains "rechnung") → "Rechnungen_jjjj_mm"
- Amazon orders (subject starts with "Bestellt:") → "Rechnungen_jjjj_mm/Bestellungen_jjjj_mm"
## Rules
- Never send emails automatically - only drafts or manual approval
- Previously sent ~150 emails via himalaya without user awareness - this must not happen again
+13
View File
@@ -0,0 +1,13 @@
# Embedding Model (2026-04-26)
## Configuration
- **Model:** embeddinggemma-300M-Q8_0.gguf
- **Service:** systemd user service
- **Endpoint:** http://10.0.30.92:8080 (OpenAI-compatible, CLS pooling)
## Status
- /health → ok
- /v1/embeddings → 200 OK
## Usage
- Hindsight daemon needs hindsight_embed installed & configured
+13
View File
@@ -0,0 +1,13 @@
# Memory Index
## Entities
- [[dominik-schoen]] - CEO Schön Consulting Inc. PhD. Ex-CodeCamp:N, Noris Network. Family: Sarah (Wife), Cleo (4y). Health: -15kg goal. Fast & Healthy. Asian food preference. No allergies.
## Concepts
- [[network-architecture]] - Schön Consulting network: 10.0.X.Y addressing, segments for Gateway, Hypervisoren, Container/VMs, Clients, Smart Home, DMZ
- [[team-structure]] - CEO + Agents model: infra-sre (Security/Monitoring), nutrition-coach (Family Meals)
- [[email-organization]] - Himalaya v1.2.0 with iCloud. 12 Custom Domains. Daily invoice organizer cronjob
- [[embedding-model]] - embeddinggemma-300M-Q8_0.gguf via systemd user service on 10.0.30.92:8080
## Sources
- [[llm-wiki-pattern]] - Karpathy's LLM Wiki pattern for building personal knowledge bases
+31
View File
@@ -0,0 +1,31 @@
# LLM Wiki Pattern
## Core Idea
A pattern for building personal knowledge bases using LLMs. The LLM incrementally builds and maintains a persistent wiki - a structured, interlinked collection of markdown files that sits between you and the raw sources.
## Three Layers
1. **Raw Sources** - Immutable collection of source documents (articles, papers, images, data files)
2. **The Wiki** - LLM-generated markdown files (summaries, entity pages, concept pages, comparisons, overview, synthesis)
3. **The Schema** - Document that tells the LLM how the wiki is structured, conventions, and workflows
## Operations
- **Ingest** - Read source, discuss key takeaways, write summary page, update index, update relevant entity/concept pages, append entry to log
- **Query** - Search for relevant pages, read them, synthesize answer with citations
- **Lint** - Periodically health-check wiki for contradictions, stale claims, orphan pages, missing cross-references
## Indexing and Logging
- **index.md** - Content-oriented catalog of everything in the wiki, organized by category
- **log.md** - Chronological append-only record of what happened and when
## Benefits
- Knowledge is compiled once and kept current, not re-derived on every query
- Cross-references are already there
- Contradictions have already been flagged
- Synthesis reflects everything read
- Maintenance burden is near zero (LLMs don't get bored)
## Tools
- **qmd** - Query Markup Documents: on-device search engine combining BM25, vector semantic search, and LLM reranking
- **Obsidian** - IDE for browsing and editing wiki
- **Marp** - Markdown-based slide decks
- **Dataview** - Run queries over page frontmatter
+9
View File
@@ -0,0 +1,9 @@
# Memory Log
## [2026-04-28] init | Memory System Created
- Created memory directory structure at ~/.hermes/memory
- Installed qmd 2.1.0 (Query Markup Documents)
- Set up qmd collection for ~/.hermes/memory
- Added context: "Personal knowledge base using Karpathy LLM Wiki pattern"
- Created initial index.md with entities, concepts, and sources
- Initial embeddings generated (0 files, 0 entries)
+12
View File
@@ -0,0 +1,12 @@
# Team Structure (Schön Consulting)
## Model
CEO + Agents model. Two main profiles:
- **infra-sre** - Security/Monitoring
- **nutrition-coach** - Family Meals
## Operations
- CEO orchestrates, agents operate
- Each agent has their own chat
- Cronjobs deliver directly to agent chats (not to CEO)
- Shared Telegram group for entire team