Skip to content

docs: refresh README (automated audit)#1

Open
rustyorb wants to merge 1 commit into
masterfrom
chore/readme-audit
Open

docs: refresh README (automated audit)#1
rustyorb wants to merge 1 commit into
masterfrom
chore/readme-audit

Conversation

@rustyorb

@rustyorb rustyorb commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Automated README audit — please review the proposed README before merging.

Generated by [repo-readme-auditor].

Summary by Sourcery

Add a top-level README describing the antigravity-memory MCP server, its capabilities, setup, and usage.

Documentation:

  • Introduce user-facing documentation covering features, tech stack, project structure, configuration, and usage of the antigravity-memory server.
  • Clarify the distinction between narrative subproject docs and this README’s focus on actual, verifiable behavior.

Copilot AI review requested due to automatic review settings July 11, 2026 07:11
@sourcery-ai

sourcery-ai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Reviewer's Guide

Adds a new top-level README that documents the antigravity-memory MCP server, including its features, tech stack, structure, setup, configuration, usage, and relationship to existing nested documentation files.

File-Level Changes

Change Details Files
Introduce a comprehensive top-level README describing the antigravity-memory MCP server and how to use and integrate it.
  • Document the server’s purpose as an MCP provider of encrypted, graph-based, persistent memory for AI assistants.
  • Enumerate key features: graph-structured memory model, AES-256-GCM encryption at rest, salience-based recall and traversal, non-destructive evolution, deprecation semantics, and automatic migration from legacy plaintext stores.
  • Describe the tech stack: Node.js ES modules, MCP over stdio via @modelcontextprotocol/sdk, flat encrypted file storage, and Node’s crypto usage.
  • Outline the project structure and key files, including memory storage layout and the encryption key file behavior and git-ignore expectations.
  • Provide installation and runtime requirements, including Node.js version and npm-based setup.
  • Detail MCP client configuration for registering the server, including example JSON pointing to index.js and first-run behavior (directory creation, key generation, store initialization).
  • Document available MCP tools and resources in tables, including arguments and behavior semantics for memory operations and statistics.
  • Clarify the absence of automated tests and suggest manual verification via npm start and MCP client usage.
  • Add a note distinguishing narrative/roleplay content in nested documentation from the technical, behavior-focused top-level README.
README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new top-level README.md intended to provide a purely technical, verifiable overview of the antigravity-memory MCP server (features, setup, configuration, and tool/resource surface) distinct from the more narrative docs under antigravity-memory/.

Changes:

  • Introduces a top-level README documenting the MCP server’s capabilities (encrypted graph memory, tools/resources, migration behavior).
  • Documents local install/run steps and an example MCP client configuration snippet.
  • Adds a “Note on Content” clarifying the distinction between narrative subproject docs and this README.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
- **Graph traversal ("reflect")** — beyond direct text matches, follows edges to surface connected memories for a topic.
- **Non-destructive evolution** — updating a memory (`evolve`) preserves the prior content and the reason for the change instead of overwriting it.
- **Deprecation instead of deletion** — `forget` hides a memory from normal recall but keeps it in the graph with a documented reason.
- **Automatic migration** — on startup, any legacy plaintext `nodes.json`/`edges.json` files are read, re-saved as encrypted, and removed.
Comment thread README.md
- **Graph-structured memory** — every memory is a node (`entity`, `episode`, `knowledge`, `procedure`, or `reflection`); nodes are linked by typed edges (`relates_to`, `derived_from`, `contradicts`, `evolved_into`, `belongs_to`, `informed_by`).
- **Encrypted at rest** — memory nodes and edges are stored as AES-256-GCM ciphertext (`memory/nodes.enc`, `memory/edges.enc`); a 256-bit key is auto-generated on first run and saved to `memory/.key`.
- **Salience-ranked recall** — text/type/tag search over memories, sorted by salience then recency, with access-count tracking.
- **Graph traversal ("reflect")** — beyond direct text matches, follows edges to surface connected memories for a topic.
Comment thread README.md
- **Encrypted at rest** — memory nodes and edges are stored as AES-256-GCM ciphertext (`memory/nodes.enc`, `memory/edges.enc`); a 256-bit key is auto-generated on first run and saved to `memory/.key`.
- **Salience-ranked recall** — text/type/tag search over memories, sorted by salience then recency, with access-count tracking.
- **Graph traversal ("reflect")** — beyond direct text matches, follows edges to surface connected memories for a topic.
- **Non-destructive evolution** — updating a memory (`evolve`) preserves the prior content and the reason for the change instead of overwriting it.
Comment thread README.md
Comment on lines +69 to +70
`memory/.key` is required to decrypt existing memories — back it up if the data matters, and never commit it (it's already listed in `.gitignore`).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants