The index reisebedingungen is built (5.1 to 5.3), the search is in place (5.2). The travel assistant of Nordlicht Reisen GmbH answers questions only with a source and hands reimbursements, legal questions and blocked accounts over to a person (R-02). This lesson hangs the retrieval into the assistant's workflow: as a tool of the agent and as a step of the application that supplies the writer and the checker (E-03) with the same sources.
Prior knowledge. The three paths from the project to the index are shown in lesson 2.2, function tools, toolboxes and MCP in lesson 2.4, workflows, approvals and the checker in lesson 2.5. Grounding, sources and refusing without a source are in "AI track, lessons T5.1 to T5.3", function calling in "T7.2", workflows in "T7.4", foreign text as data in "T6.2", hard rules in "T6.4".
New in this lesson (changes no R number). The function tool is called suche_reisebedingungen; for each question the application keeps a Quellenbuch (source ledger) that records the hits of the run; the threshold for "source" is the value 2 of the semantic ranker (assumption, 5.2).
The requirement
All numbers are assumptions of the task.
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 5.5-01 | The agent calls the search as a tool with question and language. | F | 1 tool, 2 parameters | Must | 2.4 |
| 5.5-02 | The application knows the hits used, not only the model's text. | R | source ledger per question | Must | R-02 |
| 5.5-03 | Without a hit above the threshold the question goes to a person. | R | 0 answers without a source | Must | R-02 |
| 5.5-04 | Hits reach the model as fenced-in data. | R | fence per hit | Must | R-11 |
| 5.5-05 | The checker sees the same sources as the writer. | Q | 1 search per question | Should | E-03 |
| 5.5-06 | The search needs no key. | R | 0 keys | Must | R-07 |
| 5.5-07 | The retrieval is testable without Azure. | Q | stub instead of search service | Should | R-10 |