> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pnbr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Find knowledge and its evidence

> Find relevant project records, open them in full, and quote the source passages behind their claims.

Use this when the answer should reflect both the project's structured records
and the original material those records came from.

## Before you start

* [Check the active project](/runtime/orient).
* State the question or decision you are researching.
* Name a record type or source when the topic is broad.

## Ask your agent

> Find what this project knows about enterprise procurement. Separate the
> project findings from the exact source evidence. Open the most relevant
> records in full, then quote the passages that support them. Tell me when a
> claim has no source passage.

## Steps

<Steps>
  <Step title="Find candidate records and sources">
    The agent searches project records and source metadata for the topic.
  </Step>

  <Step title="Open the strongest records">
    It reads the complete fields, relationships, and attached source references instead of relying on search snippets.
  </Step>

  <Step title="Quote the source material">
    It retrieves the passages that directly support the relevant claims.
  </Step>

  <Step title="Answer with gaps visible">
    It separates what the project records say, what the sources say, and what remains unsupported.
  </Step>
</Steps>

## Verify

A strong answer identifies the records it used and includes direct source
passages. If it only lists filenames, it has not read the evidence. If it only
quotes documents, it has skipped the structured records already in the project.

## Troubleshooting and variants

* Start with a project inventory when you do not know what it contains.
* Restrict the search by record type when the same term appears in several domains.
* Restrict source retrieval to a named document when you need a focused answer.
* Ask the agent to report unsupported claims instead of completing them from general model knowledge.

<Accordion title="Tool trace">
  ```text theme={null}
  penumbra_status
  → penumbra_omnisearch
  → penumbra_read
  → penumbra_source_rag
  ```
</Accordion>
