Decision: Implement OBSIDIAN as Go Beyond’s Organisational Memory
Date: 2026-05-01 Made by: damien Status: made — in progress
Context
Go Beyond uses Claude heavily via Cowork. Knowledge from sessions, files, and lessons was disappearing into chat history with no compounding. Damien wanted a persistent memory layer that grows smarter over time.
Options Considered
| Option | Notes |
|---|---|
| RAG / vector database | Retrieves from raw docs; no accumulation; complexity |
| Karpathy LLM Wiki (OBSIDIAN) | Compiles knowledge into structured wiki; compounds; simple markdown |
| No memory system | Status quo; knowledge stays siloed in chat history |
Decision Made
Implement OBSIDIAN — a Go Beyond-specific instance of the Karpathy LLM Wiki pattern — as the organisation’s persistent memory for all chats, files, and lessons learned.
Implementation Choices Made
| Choice | Decision | Rationale |
|---|---|---|
| Storage location | OneDrive - Go Beyond | Accessible across all machines with OneDrive |
| Initial scope | All Cowork sessions auto-ingested | Maximum accumulation from day one |
| Query output | Answer in chat AND file back to wiki | Best of both worlds |
| Go Beyond context | Seed immediately, grow from sessions | OBSIDIAN learns Go Beyond as Damien uses it |
| Multi-user | Designed for future team members | Wiki belongs to Go Beyond, not one person |
Outcome
(Update as OBSIDIAN matures)
Installed 2026-05-01. Claude CLI PATH issue pending resolution (see 2026-05-01-lesson-claude-cli-windows-path).
See Also
- concept-OBSIDIAN-llm-wiki — How OBSIDIAN works
- 2026-05-01-decision-OBSIDIAN-onedrive — Storage location decision