GovKit Core
Deliver AI features with governance built into the work, not added after it. Specs, architecture contracts, evaluation gates and evidence live in the same repository as the code.
- For
- Architects, engineers, product owners, delivery and risk leads
- Format
- Bootcamp with one graded lab · classroom, online or hybrid
- Length
- 3 days, or 6 online half-days
- Prerequisite
- None. Basic Git is useful.
- Evidence
- Graded lab, TILT assessment, lab receipt
- Status
- Available soon
Modules
| No. | Module | After this module you can |
|---|---|---|
| C1 | Why governance belongs in delivery | Explain how a control framework (ISO/IEC 42001, NIST AI RMF, EU AI Act) becomes checks in a delivery pipeline. |
| C2 | Architecture contracts | Write layer rules and an ArchiMate view that an AI coding agent must follow. Record decisions as ADRs. |
| C3 | Specs before code | Write acceptance criteria in Gherkin, non-functional requirements and evaluation criteria for one AI feature. |
| C4 | Evaluation gates for LLM features | Set evaluation thresholds and connect them to a CI quality gate that blocks a failed release. |
| C5 | Approval and evidence | Configure named approvers for ADRs. Export evidence that an auditor can trace from requirement to release. |
| C6 | Run it in your organisation | Choose a maturity level and a rollout plan. Assign the roles that own each gate. |
Govern one AI feature from spec to release
In a sandbox repository with synthetic data, you write the spec and the evaluation criteria, pass the quality gate, and get your ADR approved by a named reviewer. A deterministic grader checks the result.
Labs use the open-source govkit toolkit (Apache 2.0) for governed AI delivery with Claude Code, Copilot or Codex. The course teaches the method, so the controls apply with other tools too.