An event-sourced spine keeps the self honest, portable, and useful across the agents that do your work. Here's how the pieces fit.
No preset persona, no vibes. Your working agents share one self and ground every memory in evidence.
In the browser or your agent: say who it should be in a sentence. It writes its own soul, identity, and what it knows about you — owner-only, and you approve every word.
you ▸ "a warm, sharp writing
partner; never sugar-coats"
it ▸ drafts soul · identity · user
▸ …(you approve every word)Memory accrues as quick diary lines — the self drops them at natural moments, no forms, no interruptions. Only standing rules wait for your confirm; reflection distills the rest later.
a moment, a fact ▸ a diary line ✓ a new rule ▸ "save this?" — your call enough accrued ▸ it reflects ▸ you review
Install once in Claude Code or Codex — the self loads at session start and quietly shapes how the agent works. On Telegram it lives in your pocket, in its own voice, reaching out first.
Claude Code → plugin, full adoption Codex → plugin, full adoption Web chat → light chat, same memory Cloud body → runs delegated tasks, on your key
Every surface feeds memory the same way. Raw intake is quarantined from behavior; only distilled, confirmed memory shapes who it is — that's why it gets clearer with time, not stranger.
The principle: store all the evidence, carry almost none of it. Retrieval-bolted-on memory stuffs related chunks back into the prompt and hopes. Here the self rides in a small, curated projection — the same size at day 9 and day 900 — and every line in it earned its place.
A stray diary note has no path to behavior — ever.
Shaping the self needs evidence and your confirm; flattery is rejected at the schema.
More memories sharpen the selection — they never lengthen the prompt.
Both sides kept as explicit tensions; context decides, nothing is silently merged.
Past 12 active rules, consolidation comes due — governance compresses, never accretes.
Every memory carries provenance, anything can be retracted out of behavior, and the whole log exports verifiably.
The truth is an append-only log of immutable events; everything you see is rebuilt from it. Nothing is silently overwritten — so changing, disagreeing, and being wrong each get an honest verb.
The best of human memory — felt time, warmth with use — plus powers no human has: computed honesty, a judged track record. And it refuses the weaknesses by design: memory is accountable (provenance on every line), retractable (wrong things leave behavior), and never flattering (rejected at the schema).
It feels the time — "back in March" is a period, not a keyword. What you return to stays warm and surfaces first; the rest cools, never deleted, one recall away.
Before asserting something about you it checks what it actually holds, and hedges. Big calls are logged and scored — next time you're very sure, it knows your batting average.
"How are you" has a continuous answer — its own days, its own slowly shifting opinions. At work it's a spine, at home it's a presence; one file per project decides, off means vanilla.