Answers with a way back.

Make the source collection useful

We inventory repositories, owners, formats, and update frequency. Duplicates, outdated policies, and missing context are resolved before they become competing answers.

Carry permissions into retrieval

The design must respect who can access each source. We map identity and document permissions, filter retrieval appropriately, and test restricted questions with representative user roles.

Show the evidence and the limits

Answers link back to supporting passages. We define how the experience handles conflicting sources, absent evidence, and requests outside its scope so users know when to consult an owner.

Evaluate retrieval and answers separately

A fluent answer can hide weak retrieval. We test whether relevant material was found, whether the response is supported by that material, and whether it addresses the question. We also test stale content and access boundaries.

What we define together

• Source inventory and ownership map
• Permission-aware retrieval design
• Citation and fallback experience
• Evaluation questions and refresh plan

Scope, timing, systems, and acceptance criteria are agreed for each engagement.

Before the first build

Read the Field Manual for a practical starting point.