How to run the indexer and verify memory snapshots

The indexer accepts pending snapshots as soon as a push happens from the CLI or MCP server.

Verification happens when a git push webhook matches a pending snapshot by commit hash, turning it into a verified memory record.

This separation keeps real-time collaboration fast without compromising the audit trail.

Pending updates are great for speed but risky if they are not backed by code. Verified updates carry the audit trail teams need.

This lets the cloud layer index knowledge without owning it and keeps Git as the canonical store.

Verified memory is what powers confident retrieval for agents and reporting for managers.

Index only the memory artifacts you intend to query: tasks, decisions, and changelog data.

That keeps retrieval precise and avoids bloating the vector store with unrelated source files.

Use small, consistent summaries so the index can retrieve the right entries quickly.

Track pending-to-verified conversion time so you know when Git verification is lagging.

Monitor failed ingestion events to avoid missing memory updates after deployments.