v0.5 — Repo reorganization (docs/ folder + papers/stubs/)

What's in v0.5

This release reorganizes the repo layout so the root listing stays clean as the
paper count grows. No content was lost; it was just moved.

Repo layout after v0.5

docs/                  ← all concept docs (was scattered at root)
├── agent-memory-survey.md
├── meta-surveys.md          (was surveys.md)
├── research-radar.md        (was research-radar-spec.md)
├── taxonomy.md
├── information-sources.md
├── related-work.md
├── products-landscape.md
├── signals.md
└── ymem-binding/            ← Ymem-specific bindings (was top-level)

papers/
├── index.md
├── <9 deep notes>.md        ← URL-stable, pinned at root
├── stubs/                   ← 988 auto-generated stubs moved here
├── pdfs/                    ← 529 PDFs, 1.8 GB (unchanged)
└── _scrape/

products/                    ← unchanged

Highlights

• Root listing: 18 items → 13 items
• docs/ folder: collects 8 concept files + the ymem-binding/ subdirectory
• papers/stubs/ folder: 988 cross-list scrape stubs moved out of the
  papers/ root so ls papers/ now shows the 9 deep notes plus the index
• Renames (better naming, no information loss):
  • surveys.md → docs/meta-surveys.md (disambiguates from the living survey)
  • research-radar-spec.md → docs/research-radar.md (the -spec suffix lost
    its meaning after v0.3)
• Removed: empty impact-reports/, single-file survey/ directories

Breaking changes

External links to root-level concept docs (e.g.
/awesome-agent-memory/blob/main/taxonomy.md) will 404. New canonical paths
are under docs/. The 9 deep paper notes in papers/ kept their URLs.

Stats

• 989 papers total, scraped from 9 sibling awesome-lists, deduped
• 529 PDFs locally archived under arXiv / CC-BY / OpenReview licenses
• 10 product notes + 9 deep paper notes + 6 meta-surveys
• 1 living survey at docs/agent-memory-survey.md

Full commit

5486a9c —
1025 files changed, +1299 / −1288 (mostly git mv rename detection)

---

Maintained by the Ymem project. The
docs/ymem-binding/ subdirectory holds project-specific bindings; the
top-level docs stay product-neutral.