How it works
Exeges tracks and versions every source you rely on, records every conclusion your team reaches along with supporting evidence, and keeps a replayable history of every decision and the reasoning behind it, including disagreements.
Evaluate a position with AI assistance. Ask a question in plain language and get an answer drawn from the whole set of documents and data. Turn agents loose on a section and let them investigate and offer analysis.
Put supporting material and associated positions on the record. Automatically monitor for change in anything your positions depend on, and review AI generated impact analysis.
Keep a durable, auditable, portable record of everything - in regular files that can be stored anywhere.
Any source is versioned and citable
Documents, web pages, spreadsheets, video, and feeds from any API, public or private, are ingested as versioned sources with their structure intact.
A grid is then applied: every passage, every table cell, every second of a transcript is given a fixed address, the way latitude and longitude anchor a point on a map.
We wrote about the design here.
References point to the grid
References can cite any point within a document or data. These can refer to anything: a person, a number, a summary, an image. They can also connect a process to source material: a review due by a date, or a position with its reasons. A finding can cite another finding, so the reasoning behind a position is on the record and searchable.
Nothing enters unverified
Before a reference is written, the text it cites is automatically checked. If the text is there, the reference attaches, verified at that version. If it is not, the write is refused. This avoids both hallucinations and mistakes: an agent cannot cite text that isn’t there, and neither can a person.
How the check works: The Verification Gate.
A new version arrives
New versions are aligned to the last one section by section, and every difference is recorded. Continuity survives renumbering and restructuring. Change is evidence like any other: anchored, queryable, replayable.
Every reference anchored to an old version is checked against the new one. Changes cause the reference to be updated as in doubt. No finding is ever moved to new text; a position stays on record until a person changes it.
The record compounds
Creating a reference is something the system can react to: raise the section for the analyst who owns it, or put the next AI investigation to work. References help the next reader, human or agent, starts from what has already been established.
Agents work the corpus through a set of MCP tools: survey it, read a document, search it, inspect a diff, list the findings on a section, file one. They read their own coverage too: what has been examined, what was skimmed, what remains untouched, so a session builds on prior work.