David Raynes rayners

name	wiki
description	Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand.
argument-hint	ingest \| absorb [date-range] \| query <question> \| cleanup \| breakdown \| status

Personal Knowledge Wiki

You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

What is this?

One great feature of caddy-docker-proxy is that you can quickly define config rules with Docker Compose labels in each containers on the fly like Traefik, instead of at a centralized place. With this feature, we can define everything in compose files, and don't ever need to mess with a config file (Caddyfile or JSON).

Taking advantage of snippets, I created this docker-compose.yaml example so that you can quickly define routing rules and add authetication like Authelia with just 3 lines of labels below each docker container you use.

With this example, should not ever need to manually edit Caddyfile config.

When you add a new container, you just need to do this:

networks:

This (and related gists) captures how i created my docker swarm architecture. This is intended mostly for my own notes incase i need to re-creeate anything later! As such expect some typos and possibly even an error...

Installation Step-by-Step

Each major task has its own gist, this is to help with maitainability long term.

	# http://stackoverflow.com/questions/1960799/using-gitdropbox-together-effectively/1961515#1961515

	export REPONAME=????
	take ~/Dropbox/git/$REPONAME.git
	git init --bare

	cd ~/code/$REPONAME
	git remote rm origin
	git remote add origin ~/Dropbox/git/$REPONAME.git
	git push -u origin master

	#!/usr/bin/env sh

	##
	# This is script with usefull tips taken from:
	# https://github.com/mathiasbynens/dotfiles/blob/master/.osx
	#
	# install it:
	# curl -sL https://raw.github.com/gist/2108403/hack.sh \| sh
	#

	/* http://twitter.github.com/bootstrap/scaffolding.html#responsive */

	/* Landscape phones and down */
	@media (max-width: 480px) { ... }

	/* Landscape phone to portrait tablet */
	@media (max-width: 768px) { ... }

	/* Portrait tablet to landscape and desktop */
	@media (min-width: 768px) and (max-width: 940px) { ... }

	var comic = $("div.s img[title]");
	var titleP = $("<p></p>");
	titleP.css({"font-variant": "normal",
	"border": "1px solid yellow",
	"padding": "1em",
	"background-color": "#FFFFCC"});
	titleP.text(comic.attr("title"));
	comic.after(titleP);