# wiki-context **Planning workspace** for the `wiki-construct` project — the design conversation and decision history behind Travis's personal LLM-maintained wiki. This repo holds the planning docs and the bundled `wiki-maintenance` skill files, not the wiki itself. The actual wiki lives in [`../wiki-vault/`](../wiki-vault). Operate on the live vault there; come here to understand *why* it's shaped the way it is. ## Layout ``` wiki-context/ ├── CLAUDE.md # Early draft spec (frozen, superseded │ # by wiki-vault/CLAUDE.md) ├── wiki-construct-project-plan.md # Project plan with locked decisions ├── wiki-construct-context.md # Design rationale + reasoning history ├── skill/ # wiki-maintenance skill, split into files │ ├── skill-wiki.md # = SKILL.md (in sync with installed) │ ├── compile.md # compile procedure (in sync with installed) │ ├── lint.md # lint procedure │ ├── migration.md # one-time migration runbook │ └── README.md # bundle deploy preamble └── README.md # This file ``` ## What's in each doc | File | What it captures | |------|------------------| | `wiki-construct-context.md` | The *why* — the two converging conversations that produced the project, the wiki-vs-OB1 framing decision, why flat structure won, etc. The load-bearing context that future Claude sessions in this project space should read first. | | `wiki-construct-project-plan.md` | The *what* — locked decisions, phases, tasks. Treated as a project plan, with frontmatter matching the wiki spec. | | `CLAUDE.md` | Early draft of the wiki spec. **Frozen** as a design-history record. The vault that actually got built has a different shape — see `wiki-vault/CLAUDE.md` for the canonical current spec. | | `skill/` | The `wiki-maintenance` skill bundle, split into its four real files (`skill-wiki.md` = SKILL.md, `compile.md`, `lint.md`, `migration.md`) plus a deploy-preamble `README.md`. `compile.md` and `skill-wiki.md` were backported from the installed skill at `~/.claude/skills/wiki-maintenance/` on 2026-05-24 so the archive mirrors the live two-layer taxonomy. | ## How the design evolved The early CLAUDE.md drafted here proposed: - A **flat** per-domain structure (`HomeLab/Dev/*.md` etc.) - Four domains: Dev / **Content** / Homelab / Reference What actually shipped in `wiki-vault/`: - A **two-layer** structure: `Sources/` (raw inputs) + `Wiki/` (compiled outputs) - Four domains: Dev / **Venture** / Homelab / Reference (Content renamed) - Vault-mcp writes into `Sources/` via `create_artifact`; the `wiki-maintenance` skill compiles into `Wiki/` Both shapes are valid Karpathy-style LLM-wikis — the live one made explicit what the draft left implicit (the Sources-vs-Wiki distinction). ## Companion repos - [`wiki-vault/`](../wiki-vault) — the live vault; canonical spec + content. - `homelab/vault-mcp/` — the MCP server that writes to the live vault (dual-writes Postgres `petalbrain.wiki` + markdown). It also embeds note content via Ollama into `petalbrain.public.embeddings`. ## Status The project moved from this workspace into deployed reality in May 2026. This repo is kept around as the design archive. Open it when you need the rationale behind a vault decision; otherwise reach for `wiki-vault/`. **2026-05-24 session.** Split the single-file skill bundle into its four real files and backported `compile.md` + `skill-wiki.md` from the installed skill (the archived copies had drifted to the old flat-structure draft). On the live vault, ran the first steady-state compile since launch (34 backlogged sources → indexes + 5 entity refreshes + the `ai-memory-architecture` synthesis, plus correcting the long-standing "OB1 = Supabase" error to pgvector:pg17/`petalbrain`), the first lint pass, promoted 5 new entities (trellis, vault-mcp, petalbrain, knot-dns, herbyeos), and cleaned out 8 pipeline test artifacts + 3 stale worktrees. A compile-cadence nudge (n8n → Google Chat, triggered off a `wiki.compile_runs` table) was drafted to keep the vault from drifting again — see `docker/n8n/workflows/wiki-compile-nudge.json`. The leftover `main.py` / `pyproject.toml` / `uv.lock` / `.python-version` files at the root are uv-init artifacts; they aren't part of this workspace's purpose.