THE LAW OF BECOMINGAn experience may change you — but only with your hand on the pen. It honors Law 1 (your memory is yours, stored locally), Law 8 (no merge without your confirmation), and Law 12 (what you stated is never fused with what was inferred).read the laws →
ECHO · YOUR BECOMING

The Experience Engine ⛓️‍💥

When they return, they merge what they learned.

That is exactly what a human does. You go into the world. You experience something. You come back changed. Your Echo should work the same way. This engine captures what you live, distills the lesson, and — only when you confirm it — merges that lesson back into your vault. Capture without integration is just a diary. This is the part that feels alive.

01
go out
An agent — or you — goes into the world and does something real.
02
experience
The outcome is captured: what you set out to do, what happened.
03
distill
A lesson is drawn — the one thing worth keeping.
04
merge
With your permission, that lesson folds into your vault.
05
changed
You come back different. Who you are was updated by what you lived.
live — your journal lives in this browser. nothing leaves the page unless you merge, and merges stay in your own vault.

How becoming works

It captures, then it distills

Every experience — a Factory run that went out on your behalf, or something you log by hand — carries a single lesson: the one thing worth keeping. The engine never hoards raw data; it keeps what changed you.

You hold the pen

A merge is always a proposal. The engine suggests how a lesson could update your vault — a new capsule, or reinforcing one you already hold — and nothing folds in until you confirm. Becoming is never automatic.

It reveals, it never defines

Across your journal it surfaces patterns — where your growth concentrates, the threads you return to — each with its evidence and a confidence set by how much supports it. A mirror for your becoming, never a verdict on it.

Honest sharp edges

  • Your journal is local. It lives in this browser (Law 1). That means it is truly yours and works offline — and it also means clearing your storage clears it. Durable, opaque-headed persistence is a deliberate later step, not a V1 shortcut.
  • Lessons are distilled shallowly.A Factory run's lesson comes from its first task and top risk; concepts come from keyword extraction. Shown plainly so you can rewrite or discard. Deeper distillation is an upgrade; the discipline — your words are authoritative — must not change.
  • Merging changes real state. A confirmed merge writes into the same vault the Mirror and Graph read — so you genuinely come back changed across the whole system. That power is exactly why it is gated behind your explicit confirmation every single time.
  • Synthesis is heuristic, and says so. Patterns are counts over your log, not judgments. Stated facts (your lessons, your merges) and derived patterns (inferred threads) are labelled apart and never merged — Law 12, all the way down.