Governance Artifacts
Governance artifacts should be typed records you maintain so a sensitive activity can be defined, operated and checked.
Which artifacts you define and use will depend on which governance standards you are following. Here, we provide definitions for the 33 artifacts named by Gemara, ISO/IEC 27001 and ISO/IEC 42001, kept as one catalogue rather than three, because the standards largely describe the same records under different names.
- Definitions — the whole catalogue, one page per artifact. Each page carries the names all three standards give it, so you land on the same page whichever vocabulary you started from.
- Gemara, ISO/IEC 27001 and ISO/IEC 42001 — views onto that catalogue in each standard's own vocabulary, showing only the artifacts that standard asks for and how they connect. The two ISO sections also carry the gap analysis against Ten Factor Governance — 27001, 42001 — and guidance catalogs that re-express each standard's structure as Gemara — 27001, 42001.
- FINOS AI Governance Framework — the FINOS AIGF published as Gemara catalogs for guidance, principles, and risk vectors.
- FINOS CCC Kubernetes — Common Cloud Controls Managed Kubernetes capabilities, threats, and controls as Gemara catalogs.
- FINOS CCC Object Storage — CCC Object Storage capabilities, threats, and controls as Gemara catalogs (upstream).
- FINOS CCC Multi-Agent Reference Architecture — CCC multi-agent architecture capabilities, threats, and controls as Gemara catalogs (upstream).
- AI Portfolio Assistant — worked example with per-component Gemara twins (assistant, runtime, artifact repository).
- FINOS FOSS Contribution — Gemara catalogs and policy for employee contribution to Free and Open Source Software.
Every artifact sits in one stage of the governance lifecycle — define, assess, decide, operate, evaluate, enforce, assure, or cross-cutting if it is referenced from all of them. That stage is what the colour banding on each page and diagram represents, and it means the same thing in every catalogue.