Implement first version of the KI register (practical solution)

### Description

### Background

We need a practical, low-friction KI register that KITT can operate and teams actually use. Start simple, then evolve.

### In scope

_No response_

### Out of scope

_No response_

### Additional Information

_No response_

### Tasks

### Tasks

- [ ] Choose initial implementation (e.g. Confluence page, SharePoint list or simple YAML/JSON in repo).
- [ ] Implement the structure according to `/guides/ai-register-model.md`.
- [ ] Add at least 2–3 example entries (real or anonymised) based on current AI initiatives.
- [ ] Document:
- [ ] How to add a new entry
- [ ] Who owns maintaining it (KITT)
- [ ] When it should be updated (e.g. at start of experiment and when moving to pilot/production)
### Definition of Done

- [ ] KI register is live and accessible for BOD.
- [ ] KITT knows who keeps it updated.
- [ ] At least one team outside KITT has an entry in the register.

Start by reading guides/ai-register-model.md, then clarify which initial implementation is approved because the issue lists Confluence, SharePoint, and YAML/JSON as alternatives. Define the register structure, ownership, update timing, example entries, accessibility for BOD, and the conditions in the Definition of Done before implementation.

Written by the indexing model from the issue text.