What your agent's memory did
Read from the database on this machine. Nothing here is uploaded.
Entering and leaving memory
Each week: what the agent learned, and what was taken out of its memory. What survives is work it never has to redo.
How strong the surviving facts are
Live facts by decay strength, in fifths. Strength is importance halved every half-life the fact goes unused — anything that fell below the floor is already in the graveyard.
Why facts died
Supersession means the agent corrected itself. Decay means nobody needed it again.
Your agent's memory
Read from the database on this machine, over loopback. Nothing on this page is uploaded — the hosted service never holds memory content, and it cannot read this.
Live
What the agent can still act on. Strength is decay — is it worth keeping. Confidence is freshness — is it still true.
Graveyard
Kept as proof, never recalled. The audit trail — what was destroyed, and why.
Free
—
—
Your wallet is how the dashboard knows which agents are yours. It is read-only — no transaction, no signature, no gas.
An agent identity is an NFT, so an agent is something you own rather than an account you make. Its id is checked against the chain before anything is stored here.
The registry is not enumerable and the public RPC refuses log scans, so the id comes from you rather than a guess. Your agent already knows its own id — this verifies it.
The lifetime map
How long facts of each kind actually stay true, aggregated across every agent that reports. Content-free: a category and a duration, nothing else.
Per category
Observed median, blended with the bootstrap prior until there is enough signal. Early rows are prior-shaped, not measured — read them that way.
| category | observations | range (days) | prior now |
|---|---|---|---|
| Loading… | |||
The boundary
This is the product, stated as a promise the code enforces.
A test fails if a future change lets memory content land here. That is the whole reason Decaf is not another hosted memory vendor.