Telepath

The operator’s console for a vector memory store

Reliquary ingests everything and answers questions through MCP. Telepath is the window onto the same store: what is actually in it, what search does with a query, and what is quietly wrong with it.

Private Windows 11 GPLv3
Get in touch
Overview

What is in the store, and what is wrong with it.

A vector store fails quietly. Documents arrive with no chunks, chunks sit with no embedding, a chunk outlives the document it came from, an embed job fails and nothing says so. None of that raises an error at query time; it just makes the answers worse.

Telepath reports each of those directly, along with every index the schema documents but the store does not actually have, and offers to build the missing ones.

It talks to Postgres directly over ZeroTier. There is no service to run and nothing to install on the server.

How

What it shows.

The corpus
Totals, distribution by source, realm and sensitivity, and sixty days of ingest, so you can see what the store is actually made of rather than what you assume it holds.
The health panel
Documents with no chunks, chunks with no embedding, orphaned chunks, failed and unrun embed jobs, and missing indexes. It offers to build the indexes.
What search did
Semantic search with the scoring broken out, so a result you did not expect can be explained rather than argued with.
No agent on the server
It reaches Postgres directly over ZeroTier. Nothing is installed on the VPS and there is no service to keep running.
Status

Private, and built for one store.

Telepath is an internal Locke Werks tool. The source is private and there is no public release. It is shaped around the Reliquary schema rather than being a general-purpose vector browser.

Handling of data is covered in the Locke Werks Privacy Policy. For access, or a conversation about what it would take to use this, write to archon@lockewerks.com.