How an answer is built.

Your question is matched against every passage in the documents you can open, by meaning and by exact terms. A question about "leave for contractors" finds a clause titled "Paid time off, non-employees", and a question about "PO 4471" finds that exact number.

• Permissions are applied before any passage is read, not after.
• Headings, tables and sheet rows are kept with their passages, so context is not lost.
• Newer versions of a document rank above older ones with the same title.

The answer is written from the retrieved passages and nothing else. General knowledge is not mixed in, so a policy question gets your policy, not a typical one from the internet.

Answers stay short. Most are two to four sentences, with a list when the source itself is a list.

Each sentence carries a number. The number resolves to the document title, the section heading, and the page, slide, sheet row or email date. Hover to read the passage. Click to open the source in its own system.

A sentence that can't be tied to a passage is removed before the answer is shown.

When the documents can't support an answer, you get a clear not found instead of a confident guess. It is triggered when:

• No passage you can open is relevant to the question.
• Passages mention the topic but don't answer what was asked.
• The only relevant document sits in a folder you don't have access to. It is not named.

Where it helps, the closest document is named with a plain note on what it does cover. Admins see a list of not found questions, which is often the best map of what is missing from the handbook.

Deleted files leave the index on the next sync and are never cited again.