Specs can be inferred.
Lore cannot.

$uvx llre

Recent lore — example

LV3 · RULE

RLS policies are fail-closed — no policy means no access

LV2 · FIX

Embedding cache invalidates only on lore change, not per request

LV2 · DECISION

Chose polling over websockets for the sync MVP

Three steps, then it's automatic Read the docs →

01 · INSTALL

$ uvx llre

02 · CODE AS USUAL

03 · NEXT SESSION

> brief() → context restored

How it works

lore

the why

AI records decisions, rules, and trade-offs as it codes. Code is the current state; lore is why it got there.

doc

living design

Design notes with a checklist. Progress is tracked, and docs stay linked to the lore behind them.

cluster

the graph

lore and docs link both ways. One brief() call restores the whole web of context next session.

linklore

EARLY ACCESS

Give your AI a memory

A paid service, free during early access — converts at general launch.