Verify KI Hub Information Architecture

## Goal
The KITT team and designer reach a documented, shared agreement on the information architecture for KI Hub V2 — establishing the structural foundation before any content, navigation, or learning path work begins in M2.

## Background
KI Hub is expanding from a component register into a broader resource serving multiple user roles across Digdir/BOD. Before building content structure, navigation, or role-based entry points, the team needs to agree on a structural model. This is a decision-making and alignment task. The output is a confirmed, documented IA decision — not a built feature.

## What needs to be decided in the alignment session
- How content is organised and navigated (role-based, topic-based, or hybrid)
- Which roles are prioritised as entry points and how many to launch with initially
- What the content taxonomy looks like — how content is tagged and filtered
- Whether a "view all" path exists alongside any role-specific navigation
- Phase scope: what is in the initial launch vs future iterations

## Notes on reference material
Prior drafts have explored a two-axis model and referenced other Norwegian public sector hubs (Oslo kommune Origo, NAV Oh-My-Nav) as inspiration. These are candidate inputs to the alignment session — not confirmed decisions. They should be presented during the session and adopted, adapted, or rejected based on team agreement.

## Acceptance Criteria
- The KITT team and designer have held an alignment session and reached explicit agreement on the IA model
- The agreed decisions are documented and accessible to all team members — sufficient for developers and content editors to work from without revisiting the same questions
- The documentation covers: structural model, taxonomy, role entry point scope, and phase approach
- Existing content is assessed against the new structure so migration scope is understood
- Follow-up stories are created for any build work that results from the agreed IA
- This issue is not closeable by PO alone — it requires sign-off from both the designer and at least one developer who will implement against the agreed structure

## Prerequisites
⚠️ Prerequisite: The designer must be available and actively involved in the alignment session. This story cannot close on PO input alone. Schedule the session before this issue is moved to active.

## Dependencies
- Designer must be available for the alignment session
- Outcome of this issue directly unblocks #55–58 (learning paths and role-based navigation stories)