How transcript becomes memory
Every line here was written by the distiller at ingest, not inferred later. A memory is linked to the session chunks it was distilled from, and to the memory it replaced when a fact changed.
Lineage
● distilled memory
● session chunk
● retired (superseded)
· scroll to zoom, drag to pan, hover a node for its full text
Proxy –
Hook –
Daemon –
Agents –
Portfolio
Token Savings
–
– → –
Memories
–
– chunks · – global
Recalls
–
hook + proxy
Projects
–
compressed by type
Tokens saved (lifetime)
–
Projects
| Project | Chunks | Memories | Tokens | Status |
|---|
Recent recalls
| Time | Agent | Project | Query | Hits | Score | Tokens | Latency | Status |
|---|
Does recall reduce work?
–
measuring…
Compression
–
Recall activity
Hits
Miss
Efficiency
Avg tokens / turn
–
all sessions
Coverage · Latency
– · –
– sessions ·
Agent
BYOK proxy
–
Recalls
–
events
Hit rate
–
– hits
Avg latency
–
recall pipeline
Proxy saved
–
no proxy data
Contributed to the shared layer
Chunks written
–
– tokens
Projects covered
–
–
| Project | Chunks | Tokens |
|---|
Recall volume
Cumulative savings
–
Recent recalls
| Time | Project | Query | Hits | Score | Tokens | Latency | Status |
|---|