Nordlicht Reisen GmbH (AI-103, R-01) wants to introduce the group-travel team: From a request of 10 or more people (M-01) a checked draft is to arise that a trip planner approves (M-02). Every lesson has answered one question; now the answers lie side by side, and in some places they do not fit together. This project arranges them into a decision folder, resolves the conflicts, draws one architecture overview and writes one Bicep sketch. It stays paper: Nothing is deployed.
Prior knowledge. All lessons 0.1 to 4.7 of this course; they are not repeated, the folder refers to them by number. Recording decisions is taught by "K4, lesson 4.1.3", the presentation of an architecture by "K4, lesson 4.1.4". You know the form (folder, sheet, conflicts, sketch) from "AI-103, lesson 6.1" and "AZ-305, lesson 7.1".
New in this lesson. (1) The practice group is called rg-ai500-abschluss. (2) The names of the data services that the lessons left open: cosmos-nordlicht-<umgebung> (database gruppenreisen), sb-nordlicht-<umgebung>, srch-nordlicht-<umgebung>, kv-nordlicht-<umgebung>. (3) The sheet A-01 to A-08 and the ranking below apply only to this project. (4) The resolutions K-1 to K-6 change the lessons named for the case from here on; the lessons themselves stay as they are.
The decisions of the lessons
The column "changes" names where a row deliberately changes an earlier assumption (resolution in Solution 1).
| No. | Area | Decision | Lesson | changes |
|---|---|---|---|---|
| D-01 | 1 | Seven agents, planer as the center, levels A0 to A2, never A3 |
1.1 | |
| D-02 | 1 | Twelve channels: six intern, four mcp, one suche, one a2a |
1.2, 2.11 | |
| D-03 | 1 | Three memory tiers, mandantId everywhere; teamzustand 30 days |
1.3, 2.4 | |
| D-04 | 1 | chat: planer, recht, texter, pruefer; chat-klein: unterkunft, transport, kalkulation |
1.4 | |
| D-05 | 1 | One identity per role, matrix as data with a test; pruefer without tools |
1.5, 2.6 | 1.5 (K-3) |
| D-06 | 2 | Prompts as files, handoff JSON, context budget per role, no fine-tuning | 2.1 to 2.3 | |
| D-07 | 2 | Two indexes, wissen_suchen, scope in the code, one source ledger per run |
2.5 | |
| D-08 | 2 | Tools verfuegbarkeit_lesen, vorreservieren (A2), preis_berechnen, buchung_lesen |
2.6, 2.7 | 1.1, 1.5, 2.10, 3.1 |
| D-09 | 2 | Servers func-lieferanten, app-rechner, buchungen behind apim-nordlicht |
2.7 | |
| D-10 | 2 | Three stages in code, one revision, at most 3 approvals, 15 minutes waiting time | 2.8, 2.9 | |
| D-11 | 2 | Cache only for availability (2 minutes); 6 replicas, 4 runs per replica | 2.10 | 1.4 (K-1) |
| D-12 | 2 | Partner reederei via A2A with PartnerSchutz; ideenlabor stays outside |
2.11, 2.12 | |
| D-13 | 3 | 60 cases plus extension set, change gate, review sheet of the planner | 3.1, 3.2 | |
| D-14 | 3 | One trace per run, own attributes, alerts in two stages, regression rule | 3.3, 3.4 | 4.6 (K-5) |
| D-15 | 3 | 25 calls and 200,000 tokens per run, usage ledger, 99 % in 10 minutes | 3.5 | |
| D-16 | 4 | Run token, gate forms x-mandant-id; key in the Key Vault |
4.1, 4.2 | |
| D-17 | 4 | Scan in rg-ai500-rotteam; gr-<agent>; limits FG-1 to FG-4 in code |
4.3 to 4.5 | |
| D-18 | 4 | Pins except dev, canary in code, blue/green; ai-nordlicht-<umgebung> |
4.6 | M-09 (refined) |
| D-19 | 4 | Stages pr, test, abnahme, prod; gate with four numbers; release entry |
4.7 | 4.7 (K-2) |