The group-travel team of Nordlicht Reisen GmbH does not work through a request in one go (M-01, M-02). The planer breaks it down, unterkunft and transport search in parallel, texter and pruefer come later, and a trip planner approves. Minutes or days pass in between. Who remembers that the club prefers the train to the bus? And who prevents an attachment with a hidden instruction (M-12) from having a say in every run tomorrow? The lesson builds the memory from the three levels of F-03 and settles who may read it, who may write it and how long it may live.
Prior knowledge. "AI track, lesson T7.5" distinguishes history, state and long-term memory, shows AIContextProvider and ChatHistoryMemoryProvider, the scope with UserId and the deletion of a person. That is not repeated here. The design of the three levels is shown in lesson 1.3 of this course, the management of context in the run in lesson 2.3. New here is the build for several agents: write rights, origin of a statement, lifetime and the comparison with the service of Foundry.
New in this lesson. The team state (container teamzustand, partition key mandantId, F-03) knows four kinds of entries: anfrage, entwurfstand, notiz and vorlieben. Only the planer writes anfrage, entwurfstand and vorlieben; the specialist agents unterkunft, transport and kalkulation write only notiz. vorlieben (for example "train instead of bus") arises only from a statement of the trip planner after the approval (M-02), never from a tool result. Lesson 1.3 settles the lifetime; the exercise calculates with 30 days after the last change (assumption of the task). The long-term memory in the index gedaechtnis is fed from the vorlieben; its search is shown in lesson 2.5.
The requirement
All numbers are assumptions of the task.
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 2.4-01 | No run reads or writes data of another customer. | R | 0 hits with a foreign mandantId |
Must | M-07 |
| 2.4-02 | Each kind of entry has exactly one writing agent. | R | 0 write accesses outside the table | Must | Quality |
| 2.4-03 | What a tool or an attachment delivers never becomes a "preference". | R | 0 entries with origin tool | Must | M-12 |
| 2.4-04 | Notes expire on their own, preferences only by deletion. | F | 30 days after the last change | Must | F-03 |
| 2.4-05 | All data of a customer can be deleted and the deletion checked. | R | 0 entries afterwards | Must | Data protection |
| 2.4-06 | The rules are testable without an Azure account. | Q | stub instead of Cosmos DB | Should | F-06 |