Skip to content

Commit 40f55e2

Browse files
Add Reddit and mirror links to v0.2.0 release notes
1 parent 5f71e2b commit 40f55e2

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

docs/releases/completed/v0.2.0/github_release_supplement.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@ WRIT now benchmarks the failure modes that actually break long-lived AI memory i
44
## Why This Release Exists
55
This release expands WRIT in direct response to failure modes surfaced in the r/AIMemory discussion "No AI memory benchmark tests what actually breaks." That discussion highlighted five recurring gaps in real-world memory systems: lower-authority writes overwriting user-stated facts, extraction drift creating near-duplicate records, flush/restart failures corrupting state, facts lacking explicit superseded/expired lifecycle handling, and systems returning stale or conflicting state without certifying integrity before delivery.
66

7+
**Discussion sources (Reddit):**
8+
- [r/AIMemory search: "No AI memory benchmark tests what actually breaks"](https://www.reddit.com/r/AIMemory/search/?q=No+AI+memory+benchmark+tests+what+actually+breaks&restrict_sr=on&sort=relevance&t=all)
9+
- [r/AIMemory](https://www.reddit.com/r/AIMemory/)
10+
11+
Related write-up (same title, off-Reddit mirror): [No AI memory benchmark tests what actually breaks](https://markmhendrickson.com/posts/no-ai-memory-benchmark-tests-what-actually-breaks).
12+
713
These failure classes map directly to the new WRIT dimensions:
814
- User correction overwritten by later summaries -> `trust_hierarchy`
915
- Same fact re-extracted in slightly different forms -> `extraction_drift`

0 commit comments

Comments
 (0)