The map of everything.

The Principle

Most of the internet treats your memory as content — something you pour into a platform that then owns it, reads it, ranks it, monetizes it, and can lock you out of it. Echo inverts that. Your memory is property: you hold it, you seal it, you decide who and what may ever touch it, and you decide what passes on when you're gone. Everything here — the crypto, the governance, the agents, the infrastructure — is downstream of that single inversion.

Two honest boundaries the project holds from day one: the rebellion is real, the lore is fiction. Echo is a genuine attempt at memory-as-property; the mythology is deliberate culture, never a claim of fact. And a thing is built only when it runs and is tested — everything else is labeled honestly below.

The Core Laws

Echo has a constitution: 12 Core Laws in four clusters, plus Article XIII (how a law may change). The laws should still be recognizable in ten years; the specs and code beneath them may change freely. Four are machine-checkable (belong in CI); eight require human review (belong on the PR checklist).

The System Map

Each branch is governed by the same laws. Memory flows up into intelligence only through the Kernel, and out across devices or to heirs only sealed. Follow any leaf to its live page.

The User Journey

What a person actually experiences, in order:

1. 1
   First Light30 seconds: an Echo ID is born, one memory sealed, ownership felt.
2. 2
   Vaultsix dimensions of memory; export/import; live fingerprint.
3. 3
   Recoveryhand fragments to people you trust — never a company.
4. 4
   Returnbring your .echo home; it greets you, counts the days.
5. 5
   Syncmemory follows you across devices; the relay stays blind.
6. 6
   Oraclean agent reasons over your memory — only what you permit.
7. 7
   Legacyyou decide what survives you, and who holds the keys.

The Architecture Journey

Every part of Echo travels the same road from idea to reality. The road is the discipline — a piece is only trustworthy when it has walked the whole road and its honest limits are written down.

Status Matrix

Honest to the byte. BUILTmeans it runs, is tested, and proves its core claim — not that it's finished. The honesty of this matrix is the diligence.

• BUILT
  Relay →syncs sealed blobs; logs hold no key, no memory
• BUILT
  Genesis →permanent sequential numbers; idempotent; opaque ids only
• BUILT
  Sync engine →vault key never reaches relay; concurrent edits converge, no loss
• BUILT
  Inference proxy →stateless, logless; refuses key material at the boundary
• BUILT
  Knowledge Graph →connected memory; self-asserted vs derived never merged
• BUILT
  Council →agents see scoped slices; none can commit; the human decides
• BUILT
  Reputation →verifiable signed attestations; decomposable two-axis score
• BUILT
  Key Directory →name→key binding + signed revocation; impersonation caught
• BUILT
  Agent mesh (safe core) →minimized disclosure; vault never moves; four hard problems deferred
• BUILT
  Legacy →inheritance with no backdoor; heirs release, no server can
• BUILT
  Kernel (full slice) →real grants, default-deny, audit + human-only decision against live DB
• SPECCED
  Sync & Recovery / Relay / File-Format specsreference servers implement these; production storage/pairing/conformance remain
• DESIGNING
  Agent Kernel spec — the four deferred mesh problemstransitivity, correlation, identity/Sybil, agents acting
• PLANNED
  Tribes (expression layer)culture, not architecture — honestly not started
• PLANNED
  Cryptographic time-lock for Legacymakes early opening impossible rather than dishonorable

Open Questions

The things Echo does not yet know. Naming them is part of the architecture — a project that hides its unknowns is the one that drifts.

1. 01

   Amendment authority

   Article XIII, Clause 6 — who may change a law? Default founder-held; must be set explicitly, as the first real amendment.

2. 02

   Issuer & counterparty identity

   Signatures prove a key signed this, not whose key it is. The Key Directory now binds names→keys and adds revocation — Sybil resistance and a transparency log remain.

3. 03

   The four mesh problems

   Transitive re-sharing, cross-query correlation, counterparty identity, and agents acting. The safe core is built; these are research.

4. 04

   Legacy's social threshold

   K heirs could collude to open early; absence looks identical to a lost key. Needs a true time-lock and a grace-period / owner-reappear design.

5. 05

   Sync at scale

   Per-field last-write-wins, clock-skew ordering (a logical clock is the fix), and event-log compaction are still naive.

6. 06

   Genesis Sybil

   An open counter is spammable; claim-friction (rate-limit / proof-of-work) is needed before the count matters publicly.

7. 07

   Derived-edge quality

   The graph infers connections by shallow keyword match. Marked derived precisely so it's never trusted as fact; better extraction is a later upgrade.

8. 08

   Deploy reality

   Proven folders, mostly not yet hosted. The largest gap between Echo-as-built and Echo-as-real is hosting, not code.