lab log · n=1
RELEASES, WHEN I TRUST THEM WITH MY OWN MEMORY.
This project has exactly one user so far: me. Versions land here when they have survived my own corpus, not when a roadmap says so. No schedule is promised, and nothing is ever pushed — subscribe by RSS if you want to know. That asymmetry is the product: you pull, it never calls you.
Reclaim your history
- History import — official ChatGPT and Claude exports ingested, deduplicated, filtered by your constitution. Day one, your memory already knows years of you.
- One-gesture daily log — dictate from the iOS share sheet with an editable review step before it sends; audio transcribed overnight.
- Time capsules — seal a message to your future self; it surfaces in conversation on the day, never as a notification.
- Founding interview, self-conducted — four in-conversation sessions (biography, values, decisions, relationships); the system ingests its own transcript at the end.
- Yearbook generator — your year as a printable book, written from your own memory.
- Ollama backend — consolidation can run 100% locally, no external service at all. The exit is the feature.
- Encrypted off-site backups (restic) wired into the daily job.
Tested on my own corpus, nightly since the first commit.
The deep layer
- Bi-temporal knowledge graph — contradicted facts are closed with validity intervals, never deleted. "What was true in 2024?" is a query, not a reconstruction.
- Voiceprints — explicit enrollment plus speaker diarization; channel metadata always beats the model.
- Timeline web app, mirror tool, and a persona compiler whose proposals only take effect once you ratify them in Git.
- Fidelity harness — blind-quiz the system against its own memory, scored per life domain. Trust is earned in points, not granted by time.
The substrate
- Append-only event log —
UPDATEandDELETEdisabled at the SQL level. The past is not editable. - Sleep cycles — nightly consolidation, weekly REM recombination, active forgetting, reconsolidation of corrected memories.
- MCP server (recall, mirror, daily_log, curate, landmark, capsule) and the media pipeline: word-aligned transcription, vision, EXIF, document parsing.
- Executable constitution — exclusion perimeter enforced at ingestion, outbound actions rejected, every action audit-logged.
WHY AN n=1 LAB
A memory engine can only be judged by living with it. Every capability here exists because the absence of it hurt, in my own use, on my own server. What does not survive that test does not ship — and the honest verdict, when it comes, will be published here too.