This example finds decisions about a project and summarizes what is settled and what remains open. It reads source content without changing the original records.
Before you start
Use an installed Indra instance with access to the relevant project sources. If you are using an agent, connect its MCP client. For direct use, set your existing Vault path in a terminal:
indra_root='/absolute/path/to/your-existing-vault'
A command can start the configured background host, whose automatic sync may independently collect source records. Read Sync information before starting it if you want automatic full collection disabled.
The SQL examples below search information already retained in that Vault. A connected app can have usable live data even when the Vault contains no records from it. Tools overview explains which route to choose.
Find decisions and verify the summary
-
State the result
Give your agent a request such as:
Find the current decisions about the website redesign in my connected project sources. Summarize what was decided and what is still open. Cite each decision and leave the originals unchanged. Use the project and account already established in this conversation.
If you are working directly, write down the same subject and boundaries before searching. Replace “website redesign” in the following query with your actual project term.
-
Check the available information
Inspect the source inventory and stored record counts:
Shell indra --root "$indra_root" manage --json '{"what":"sources"}' indra --root "$indra_root" search --sql 'SELECT source, COUNT(*) AS records FROM z_records GROUP BY source ORDER BY source'These answer different questions: the first reports current source availability; the second counts retained records. Neither proves that every project document or recent change is present.
If a needed source is disconnected, follow Connect a service. Preserve any disabled source or explicit exclusion. If the source is connected but its records are absent, use a supported live read or app action, or a deliberately chosen sync.
-
Find candidate records
This parameterized query returns a small set of matching titles and excerpts:
Shell indra --root "$indra_root" search --json '{"sql":"SELECT id, source, source_id, title, substr(body, 1, 1600) AS excerpt FROM z_records WHERE title LIKE ? OR body LIKE ? LIMIT 12","params":["%website redesign%","%website redesign%"]}'Read the returned
id,source,source_id, title, and excerpt. A match is a candidate, not yet a verified decision. These queries do not rank results by importance or establish which decision is latest.An agent can perform the same query with
indra.search, using the samesqlandparamsobject. If the first terms find nothing useful, try the actual project name or a specific decision term rather than expanding immediately to unrelated sources. -
Read the evidence
Use an actual returned record ID:
Shell indra --root "$indra_root" search --json '{"sql":"SELECT id, source, source_id, title, body FROM z_records WHERE id = ? LIMIT 1","params":["<returned-record-id>"]}'The query asks for that record's stored body; a stored record may still be a partial representation of the source. Follow its source identity through an available source read when more context or current state is needed. Read live data and verify sources explains that step.
For each candidate, identify the decision, its scope, and any later correction. Keep proposals, unresolved discussion, and final decisions separate. If two records disagree, compare their context and chronology; do not silently choose whichever appeared first.
-
Produce the summary
Organize the result around the question:
- Decisions: what was decided, what it applies to, and a supporting source.
- Open questions: what remains unresolved and the relevant discussion.
- Coverage: any inaccessible or missing source that could change the conclusion.
Put each reference beside the claim it supports. Use a source link when available; otherwise retain the exact record and source identifiers so the evidence can be found again. Label an inference as an inference.
The agent should return this synthesis, not just a list of search matches. When working directly, you can use the same structure for your notes.
-
Check one important conclusion
Open the supporting record or source and verify that it says what the summary claims. Check the date and scope when calling something current or latest. If the evidence is incomplete, qualify that specific conclusion.
You are finished when the useful decisions and open questions are supported and material gaps are visible. If you next want to change a project document, specify that destination and change as a new action. Write a useful task brief provides examples.