fix(ms-ai-architect): Foundry URL-navnerom-migrering (ai-foundry → foundry/foundry-classic, 141 filer)

Task #5 del 1/3 (URL-migrering). Verifiseringen motbeviste STATE.md-premisset om ren prefix-swap: rebrand er per-URL, ikke mekanisk. En blind sed ai-foundry→foundry ville lagd 56 nye 404-er (classic-stiene finnes ikke under nytt foundry/-prefiks — bekreftet empirisk).

Metode: resolverte alle 237 unike KB-URLer mot live redirects (curl -L), bygde full-URL→full-URL-mapping fra faktisk url_effective. Bevarer locale-form, query (?view=) og #fragment per lenke.

- 231 navnerom-erstatninger over 141 filer (408 forekomster):
  - 161 → azure/foundry/ (98 ren prefix-swap + 10 sti-reorg + reorg-tilfeller)
  - 69 → azure/foundry-classic/ (eldre hub-spor: assistants, hub-DR, on-your-data; faktisk redirect-mål per operatorvalg)
  - 1 → azure/foundry-local/

- 2 døde lenker (404) fikset til verifiserte mål:
  - agent-service → azure/foundry/agents/overview
  - concepts/evaluation-evaluators/ → azure/foundry/how-to/evaluate-generative-ai-app

- 5 path-/display-referanser (uten https://, i backticks/lenketekst) rettet manuelt.

- 6 slug-baserte ai-foundry-treff urørt (scope-grense): managed-grafana-dashboard, security-baseline, power-platform prompt-builder, architecture baseline-chat (sistnevnte slug-rebrand i annet navnerom — mulig fremtidig funn).

- Parkert til task #5 del 2/3: Norway East GPT-5-datasuverenitet-fiks + modellkatalog-utvidelse (5.3/5.4/5.5, gpt-oss, sora-2).

Verifisert: 0 gjenværende azure/ai-foundry/-navnerom i skills/. validate-plugin.sh 219 PASS. test-kb-integrity.sh 117/117 passed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01REiKFhP4w6xGXXqWKpPCJJ
This commit is contained in:
Kjell Tore Guttormsen 2026-06-18 13:37:06 +02:00
commit dd1036ab8a
141 changed files with 399 additions and 399 deletions

View file

@ -142,7 +142,7 @@ Kunden må ha implementert alle mitigations (tiltak) som kreves i Azure OpenAI-d
For å opprettholde CCC-dekning må kunder implementere følgende universelle mitigations:
**1. Metaprompt (effektiv fra 1. desember 2023):**
Kundens løsning må inkludere en metaprompt som instruerer modellen til å forhindre opphavsrettsbrudd i output. Eksempel på anbefalt metaprompt finnes i Microsoft Learn: "To Avoid Copyright Infringements" i [System message framework and template recommendations for Large Language Models (LLMs)](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/system-message).
Kundens løsning må inkludere en metaprompt som instruerer modellen til å forhindre opphavsrettsbrudd i output. Eksempel på anbefalt metaprompt finnes i Microsoft Learn: "To Avoid Copyright Infringements" i [System message framework and template recommendations for Large Language Models (LLMs)](https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/system-message).
**2. Testing and Evaluation Report (effektiv fra 1. desember 2023):**
Kundens løsning må ha vært gjenstand for evalueringer (f.eks. guided red teaming, systematisk måling, eller annen ekvivalent tilnærming) ved hjelp av tester designet for å oppdage output av tredjepartsinnhold. Betydelig løpende reproduksjon av tredjepartsinnhold oppdaget gjennom evaluering må adresseres. Rapporten over resultater og tiltak må oppbevares av kunden og gjøres tilgjengelig for Microsoft i tilfelle krav.
@ -243,11 +243,11 @@ Når du veileder norsk offentlig sektor om AI og opphavsrett, vurder disse spør
- [Commission launches consultation on protocols for reserving rights from text and data mining under the AI Act and the GPAI Code of Practice](https://digital-strategy.ec.europa.eu/en/consultations/commission-launches-consultation-protocols-reserving-rights-text-and-data-mining-under-ai-act-and)
### Microsoft Learn-kilder
- [Customer Copyright Commitment Required Mitigations | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/customer-copyright-commitment?view=foundry-classic)
- [Data, privacy, and security for Azure Direct Models in Microsoft Foundry | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/data-privacy?view=foundry-classic)
- [Transparency note for Azure OpenAI | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/transparency-note?view=foundry-classic)
- [Azure OpenAI frequently asked questions | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/faq?view=foundry-classic)
- [System message framework and template recommendations for LLMs | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/system-message)
- [Customer Copyright Commitment Required Mitigations | Microsoft Learn](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/customer-copyright-commitment?view=foundry-classic)
- [Data, privacy, and security for Azure Direct Models in Microsoft Foundry | Microsoft Learn](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy?view=foundry-classic)
- [Transparency note for Azure OpenAI | Microsoft Learn](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/transparency-note?view=foundry-classic)
- [Azure OpenAI frequently asked questions | Microsoft Learn](https://learn.microsoft.com/en-us/azure/foundry-classic/openai/faq?view=foundry-classic)
- [System message framework and template recommendations for LLMs | Microsoft Learn](https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/system-message)
---