Altinn / Altinn/kihub

Add governance metadata to tool catalogue entries

Open
#85 0 comments 0 reactions 0 assignees View on GitHub
area/tools priority/high type/user-story
Dominant language
TypeScript
Stars
5
Forks
0
Avg merge
1d 23h
Merged PRs (30d)
6

Description

## As a developer
## I want to see who owns each tool, when it was last verified, and whether it is approved for use in BOD
## So that I can trust the tools I find in KI Hub and make informed decisions about adoption without needing to ask in Slack

## Business Goal
KI Hub V2 is Digdir/BOD's authoritative source for approved AI tools. Without governance metadata, users cannot distinguish between sanctioned tools and outdated or experimental entries. This erodes trust in the catalogue and pushes users back to informal channels. Governance metadata directly fulfils the acceptance criterion in Epic 2: "Each entry has owner, status, and last-verified date."

## Acceptance Criteria
- The user can see a clear status label on each tool card: Approved / Experimental / Deprecated
- The user can see who is responsible for the tool entry (owner: person or team)
- The user can see when the entry was last verified or reviewed
- The user can filter or sort the catalogue by status
- Deprecated tools are visually distinct and explain why they are deprecated
- A tool entry cannot be published without status, owner, and last-verified date

## Prerequisites
⚠️ Prerequisite: Define the governance model — what "Approved" means, who can be listed as an owner, and how often verification is required — Owner: Project Director

## Dependencies
- Part of Epic 2 — AI Tools & Framework Catalogue (#39)
- Depends on broken link audit completing first — governance only works on clean data

## Estimate
3 days

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by resolving the governance-model prerequisite with the project director, then inspect the AI Tools and Framework Catalogue work in Epic 2 (#39) and confirm the broken-link audit is complete. Define how status, owner, and last-verified data appear, how filtering or sorting works, and how publishing enforces required metadata; done means all listed acceptance criteria are met.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.