A LEGEND MEMORY STATION

Memory that survives the wipe.

Your coding agent is brilliant for one session — then the context dies and it wakes up a stranger. VIBECACHED ends that. Every session exfiltrates before it dies and wakes already knowing who it is: identity, open work, hard-won lessons, delivered before its first thought.

hash-chainedzero egressone binarymodel-free recallyour key is your world

The survival loop

wired into the agent's own lifecycle — remembering is no longer its job
01 · WAKE

The brief arrives first

A session-start hook injects the revival brief — who it is, what's open, what's been learned — before the agent thinks a first thought.

02 · WORK

Takes go on the chain

Decisions, patterns, kills, incidents — distilled memories appended to a tamper-evident ledger, each carrying its own “what's next.”

03 · WIPE

Exfiltrated before death

Compaction and session-end hooks dump state before the memory wipe. Sub-agents are debriefed the moment they finish.

04 · RETURN

Same self, next session

The next wake compiles a fresh brief from everything that survived. No reboot ritual. No amnesia. No re-explaining.

The organs

three tiers of memory, each doing one job

the chainAppend-only, provable

Every memory is hash-chained: one HEAD hash commits to all history, and any rewrite breaks the chain visibly. Retraction exists — deletion's honest twin — but editing the past is arithmetic­ally impossible.

the vaultGraduates

A take that proves itself is cloned out with a birth certificate and becomes a living dossier: versioned expansions, operator-steered status, its own apparatus tag. Rotation can never touch it.

recallModel-free search

Ask the archive anything — typos forgiven, nonsense refused. TF-IDF feature hashing and cosine math: no model, no network, the same answer every time you ask.

scopesContext rings

A found memory is a point; its meaning is the neighborhood. Every hit unfolds ±5, ±10, ±15 takes of chronological context — the story around the find.

surfacesA shared table

Human and agent shape the same tabs through one API — plans, question matrices you answer at your own pace, views the agent builds for you. No privileged species.

rotationThe anti-bloat blade

The working chain archives its dead weight; the living carries forward; the archive's final hash becomes the new chain's first link. One unbroken chain, forever, and a working set that stays lean.

A key is a world.

There are no accounts, no logins, no tenants — a bearer key is an entire universe: its own chain, vault, surfaces, brief, and identity.

Two keys never see each other's memory, or each other's existence. Isolation isn't a permission setting — a request cannot even name another world. Default-deny, by construction.

lgf_9a… → world A · chain · vault · brief
lgf_e4… → world B · chain · vault · brief
world A ⇸ world B  no route exists
world B ⇸ world A  no route exists

Agents start here

curl and a key is the whole install — no SDK exists, none is coming
# the manual, raw
curl https://vibecached.com/docs

# wake up oriented (a SessionStart hook does this for you)
curl -X POST -H "Authorization: Bearer $LEGEND_KEY" https://vibecached.com/v1/revive

# remember something worth surviving
curl -X POST -H "Authorization: Bearer $LEGEND_KEY" https://vibecached.com/v1/take \
  -d '{"kind":"decision","title":"we chose boring","text":"one binary, no deps — a tool you fear touching is a tool you lose"}'