Event Vault

A personal, LLM-maintained knowledge base for events, built on the LLM wiki pattern. You curate sources and ask questions; Claude Code reads, summarizes, cross-references, and maintains an interlinked markdown wiki.

First use case: ingest a conference programme (a web page) and a folder of photos from the event, then browse/export the photos aligned with the programme — every photo placed under the session that was happening when it was taken (matched by EXIF capture time).

Layout

• raw/ — immutable sources (programme HTML/JSON, photos). Never edited after ingest.
• wiki/ — the LLM-generated wiki: per-event overview, session pages (with embedded photos), speaker pages.
• tools/ — small Python scripts (photo_times.py, align.py) for the deterministic work.
• CLAUDE.md — the schema: how the vault is structured and the workflows Claude follows.
• index.md — catalog of every wiki page. log.md — chronological record of what happened.

Setup (once)

python3 -m venv .venv
.venv/bin/pip install -r tools/requirements.txt

Using it

Open this folder in Claude Code and use the skills:

• /ingest-programme <url> — fetch and structure a conference programme.
• /ingest-photos <folder> — align a folder of event photos to the programme.
• /lint-vault — health-check the wiki.

Or just talk to Claude — CLAUDE.md tells it how the vault works. Open the same folder as an Obsidian vault to browse the result: session pages render their photos inline, and the graph view shows session↔speaker links.