open/ms-ai-architect
1
0
Fork 0
Code Issues Releases 4 Activity

chore(privacy): scrub real-org references from plugin internals (phase 2)

Browse source 
Same bulk replacement applied to plugin-internal KB, examples, fixtures,
tests, and docs. Real organization names, persona names, internal system
identifiers, and domain-specific terms replaced with fictional generic
public-sector entity (DDT) and generic terminology.

Scope:
- okr/ — examples, governance, framework, integrations, sources
- ms-ai-architect/ — KB references (engineering, governance, security,
  infrastructure, advisor), tests/fixtures, agents, docs
- linkedin-thought-leadership/ — voice samples, network-builder,
  examples (genericized identifying headlines to "[your organization]")
- llm-security/ — research notes, scan report

Manual genericization beyond bulk replace:
- okr SKILL.md "Primary user / Domain" — generic Norwegian public sector
- linkedin-voice SKILL.md headline placeholder
- network-builder.md headline placeholder
- high-engagement-posts.md voice sample employer line + hashtag

Phase 3 (factual-attribution review) remains: a few KB files attribute
publicly known transport-sector docs/datasets (e.g. håndbok V440, NVDB)
to the fictional DDT after bulk replace. Needs manual semantic review
to either remove or restore correct citation without re-introducing
affiliation references.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-03 04:28:15 +02:00
commit 781d98f62f
61 changed files with 138 additions and 138 deletions
Download patch file Download diff file Expand all files Collapse all files

4
skills/ms-ai-governance/references/responsible-ai/ai-center-of-excellence-setup.md
View file

@ -507,7 +507,7 @@ Executive sponsorship tilgjengelig? ──No──> Ikke etabler CoE nå
| **Personvernombud involvement** | PVO må være involvert i AI-prosjekter | CoE etablerer fast møtepunkt med PVO. Personvernkonsekvensvurdering (DPIA) for AI. |
| **Sikkerhetslov og Beskyttelsesinstruksen** | Høyere sikkerhetskrav for sensitive data | CoE definerer sikkerhetsnivåer (åpen, begrenset, konfidensielt). Separate environments per sikkerhetsnivå. |
### Case: AI CoE i Statens vegvesen (hypotetisk eksempel)
### Case: AI CoE i Direktoratet for digital tjenesteutvikling (hypotetisk eksempel)
**Struktur:** Unified CoE
- Core team (3 FTEs): CoE Lead, AI Architect, AI Security Specialist (KI-seksjonen)
@ -515,7 +515,7 @@ Executive sponsorship tilgjengelig? ──No──> Ikke etabler CoE nå
**Ansvarsområder:**
- Strategi: AI-strategi alignet med "Nasjonal transportplan"
- Kompetanse: Opplæring i Power Platform AI for saksbehandlere (Copilot Studio for førerkort-chatbot)
- Kompetanse: Opplæring i Power Platform AI for saksbehandlere (Copilot Studio for saksbehandling-chatbot)
- Standarder: Governance for bruk av kamera-AI i trafikkovervåkning (GDPR, Politiregisterloven)
- Pilots: AI for vegvedlikehold (prediktiv analyse av asfaltslitasje via computer vision)