Relocate project into V0/ and add Redis Agent Memory landing layer

[therealaditigupta]

Purpose

This change reorganizes the repository to move the majority of the code into V0/ with its complete git history preserved to ensure a developer landing on the repo can build, test, and run it exactly as before (now from inside V0/). Nothing is deleted, relicensed, or hidden.

The new top-level README.md introduces the repo and points to the Redis-supported production path (Redis Agent Memory in Redis Iris) for teams who want agent memory as a managed service rather than infrastructure to operate themselves.

The intent is additive, not a demotion of the open-source work. V0 remains the open research foundation and reference architecture — it is the implementation the supported product is built on, and it stays a first-class, runnable, Apache-2.0 project in this repo.

What changed (high level)

• The entire tracked project — server app and the published agent-memory-client library (Python/Java/JS) — moved into V0/ as Git renames.
• The repository root became a thin landing layer: a new README.md, a top-level LICENSE, and short AGENTS.md / CLAUDE.md pointers that tell tools and agents "the code lives in V0/."
• CI, Docker, docs, pre-commit, and the devcontainer were updated so everything keeps working from the new location.

Reviewers can verify the move reads as renames with git show --stat --find-renames (history and blame are preserved per file).

Principles behind the change

• History-preserving — every relocation is a git mv, so git status shows renames (R), not delete-and-re-add. Blame, history, and PR reviewability survive intact.
• Move tooling together — Dockerfiles, Compose, Makefile, pyproject.toml, lockfile, mkdocs.yml, and docs/ all move into V0/ as a unit, so their relative paths stay valid. That confines the edits to the small set of files that genuinely can't move (workflows, root-anchored .gitignore entries, and root-discovered tooling).
• Tooling discovery beats uniformity — files whose behavior depends on living at the repo root stay at the root: .pre-commit-config.yaml, _typos.toml, .devcontainer/, .gitignore, and the root agent docs. We chose correctness over a tidy "everything moved" rule, because a uniform-looking layout that silently breaks pre-commit or the devcontainer helps no one.
• No license invention — the existing Apache-2.0 license is copied byte-for-byte into both the root and V0/. No license text was changed here; any future licensing decisions are intentionally left to review, not made implicitly by this move.
• Green before commit — lint, tests, docs build, and Docker/compose validation were run from inside V0/ before committing, so the move lands already-verified rather than "should be fine."

Validation performed (from inside V0/)

• uv sync succeeds (the agent-memory-client workspace resolves correctly at its new path).
• pre-commit run --all-files passes all hooks, including typos — confirming _typos.toml still resolves from the root when pre-commit runs from V0/.
• mkdocs build --clean --strict succeeds on the committed tree.
• docker compose config is valid for both V0/docker-compose.yml and .devcontainer/.
• Test suite collects (960 tests) and the unit subset passes. Full integration/API tests and multi-arch Docker image builds were left to CI (they require a running Docker daemon and provider API keys).

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[abrookins]

Look good! 👍