Institution Memory API
Memory reads a single name's history straight off the Trust Ledger and derives its track record, so each name's answers sharpen over time. It is a pure read that records nothing.
What it returns
For a known name the response returns known:true, times_seen, first_seen, last_seen, a verdict_history map, an outcomes block (borne_out, contradicted, unclear counts, total, and borne_out_rate), a confidence block (avg, last, trend), a weak_track_record flag, a plain-language signal, and the trust envelope.
For a name with no prior entries it returns known:false and a signal noting this is the first read on record.
When to use it
Use Memory to ask 'have we been right about this name before?' It is what the Readiness gate consults so a name repeatedly gotten wrong is held to a higher bar. A track record is called weak below a 50% borne-out rate once at least three outcomes have been reconciled.
The confidence trend reports rising, falling, steady, or insufficient based on recent versus older reads.
Notes and honesty
Memory is derived entirely from the Trust Ledger and reflects only prior reads, never the current call. It describes the track record of the read, never a buy or sell view. Offline the ledger is in-memory and resets on restart unless Supabase persistence is configured.
- times_seen, first_seen, last_seen
- verdict_history: counts per verdict
- outcomes: borne_out, contradicted, unclear, total, borne_out_rate
- confidence: avg, last, and trend
- weak_track_record flag (below 50% over 3+ outcomes)
- signal: plain-language track-record summary
curl -s 'https://api.lyramindos.com/v1/memory?symbol=AAPL' -H 'x-api-key: YOUR_KEY'
Questions
Where does the track record come from?
Entirely from the Trust Ledger: every readiness verdict and any reconciled outcome for that name. Memory reads that history and derives the borne-out rate, verdict mix, and confidence trend.
What makes a track record weak?
A borne-out rate below 50% once at least three outcomes have been reconciled. The Readiness gate then holds the name to a higher bar and can only tighten, never loosen, a verdict.
Does calling Memory record anything?
No. It is a pure read that never writes and never raises. It reflects only prior reads on record, not the current call.