Epic 7 — Cross-Team Agentic AI Pipeline Governance (BOD)

## Description

KITT's Epic 6 (#74) governs individual production agents — registry, classification, kill-switch, and related controls. It does not address the cross-team, end-to-end question of how BOD teams should use agentic AI consistently across the full product lifecycle, from product/business framing through design, development, and operations.

This gap was raised by Andreas (Director) and is currently tracked only as a high-level, department-wide ask in Altinn/team-operativ-koordinering#28, which is not connected to the KIHUB backlog. This epic operationalizes that ask as backlog-sized, KITT-scoped work.

## Business Goal

Give BOD a shared, validated way of using agentic AI across the whole delivery lifecycle, so teams stop reinventing ad hoc practices and KITT can support one known pattern instead of many.

## Scope

- Mapping current agentic-AI practices across BOD teams.
- Designing a shared end-to-end pipeline (product/business → design → development → operations) with defined roles and control points.
- Piloting the pipeline with a real, cross-functional team.
- Producing a rollout, training, and ownership plan.

Related to, and scoped down from, Altinn/team-operativ-koordinering#28 — see that issue for the original department-level ask.

## Acceptance Criteria

- Current agentic-AI practices across BOD teams are documented, with key variations identified.
- A shared end-to-end pipeline is described, with roles, responsibilities, and control points aligned to Epic 6's governance requirements.
- The pipeline has been piloted with at least one cross-functional team and evaluated against agreed criteria.
- A rollout, training, and ongoing-ownership plan exists for wider adoption.

## Dependencies

- Should be reconciled directly with Altinn/team-operativ-koordinering#28 once cross-repo access allows.
- Overlaps with Epic 6 (#74) on governance requirements: Epic 6 defines the controls that apply to individual agents; this epic defines the end-to-end workflow those controls sit inside.

## Prerequisites

⚠️ Prerequisite: Confirm with Andreas / his team how this KIHUB-tracked work should reconcile with Altinn/team-operativ-koordinering#28 — Owner: Roberto.

Start by reading Epic 6 (#74) and the related Altinn/team-operativ-koordinering#28 issue, then confirm with Andreas's team how this KIHUB work should reconcile. Done means documenting current practices, defining and piloting a shared lifecycle pipeline, and producing rollout, training, and ownership plans.

Written by the indexing model from the issue text.