Lians vs Hindsight.
Hindsight is agent memory that learns, scored on the same five invariants we score ourselves. Credit where it's strong, receipts where it isn't.
Credit first
Where Hindsight is genuinely strong.
Hindsight brings genuine temporal awareness to the dev-memory lane: timestamped retain, four parallel retrieval strategies including time-range filtering, and a reflect() operation that revises beliefs while preserving history. Its memory-bank + mental-model design is thoughtful.
Regulated-memory eval · last run 2026-07-04
The five invariants.
| Regulated invariant | Lians | Hindsight |
|---|---|---|
| Stale revision suppressed | pass | partial |
| Point-in-time (as-of) recall | pass | partial |
| Provable erasure (crypto-shred + cert) | pass | absent |
| Lookahead / backtest guard | pass | absent |
| Audit-state snapshot at T | pass | absent |
| Score (pass = 1, partial = ½) | 5.0 / 5 | 1.0 / 5 |
Where the lanes diverge
Different jobs, different guarantees.
Two hard gaps: temporal filtering scopes event time ranges: it cannot answer “what was believed as of date X”, and there is no delete, forget, or erase API on the public surface at all, which makes GDPR-grade erasure impossible, let alone provable. Belief revision is reflection-driven, not a deterministic keyed supersession.
The honest recommendation
Which should you pick?
Choose Hindsight for learning agents that accumulate insight over time without erasure or audit obligations. Choose Lians when facts must close cleanly, erasure must be provable, and knowledge state must be reproducible at any past instant.
retain/recall map directly onto add/recall; Lians adds the as-of dimension, the audit chain, and erasure your compliance team will ask about six months in.