Anne-Julia Seitz dazz

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.

Introduction

I am writting this gist for two reasons:

I promised I will write it. Hey Dazz 👋
It seems that more than 1 (one) person has found this an interesting approach

A small preface: This was applied in an API project built with Symfony (API Platform). That is, there was no front-end, or HTML responses. This API project supports only json or json-ld. Our tests used the Symfony test-pack (PHPUnit and some Symfony helper classes).

Building Evolutionary Architectures

Chapter 1 - Software Architecture

Architecture is 'the important stuff, whatever that is' or 'the parts that are hard to change later'. An architect analyzes business, domain, and other requirements to develop solutions that satisfy a list of prioritized architectural characteristics (-ilities). We should consider time and change with respect to architecture, or evolvability.

Software ecosystems are in a state of dynamic equilibrium. New languages, tools, methods constant force new equilibriums to emerge (free OS, linux, + free operations, puppet, led to the shift to containers). The pace of change in technology is constantly and rapidly changing in unexpected ways. We should architect systems knowing the landscape will change. Make ease of change a principal of architecture, remove the 'hard to change' definition of architecture.

An evolutionary architecture supports guided, incremental change across multiple dimensions. Evolvability is a meta characteristic that

Debug your PHP in Docker with Intellij/PHPStorm and Xdebug

For your local dev, create a Dockerfile that is based on your production image and simply install xdebug into it. Exemple:

FROM php:5

RUN yes | pecl install xdebug \
&amp;&amp; echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" &gt; /usr/local/etc/php/conf.d/xdebug.ini \

This configuration is no longer updated

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

	[opcache]
	; Determines if Zend OPCache is enabled
	opcache.enable=1

	; Determines if Zend OPCache is enabled for the CLI version of PHP
	;opcache.enable_cli=1

	; The OPcache shared memory storage size.
	opcache.memory_consumption=512

	build:install-vendor:
	stage: build
	image: <any-image-with-composer>
	before_script:
	- composer config -g cache-dir "$(pwd)/.composer-cache"
	script:
	- composer install --ignore-platform-reqs --no-dev --optimize-autoloader --no-ansi --no-interaction --no-progress
	cache:
	paths:
	- .composer-cache/

	<?php

	// !!! Warning: for reference, not debugged

	###################################################################
	# PHP_Fourier 0.03
	# Original Fortran source by Numerical Recipies
	# PHP port by Mathew Binkley (binkleym@nukote.com)
	###################################################################

	<?php
	// not so great:
	if ($blah) {
	$doSomething;
	} else {
	throw Exception();
	}

	// better:
	// be explict