Register your first AI system
The AI system is the anchor of everything in Gamut. Registering one well makes every later step, intake, assessment, evidence, reporting, faster and more consistent.
What counts as an AI system
Section titled “What counts as an AI system”Register anything that uses AI and carries governance relevance:
- Internal applications and services that embed a model.
- Vendor or third-party AI tools your teams use.
- GenAI assistants and copilots in active use.
- Agentic workflows that take action through tools and APIs.
If in doubt, register it. An under-governed AI system is a bigger risk than an extra record.
Fields to capture
Section titled “Fields to capture”| Field | Why it matters |
|---|---|
| Name | A clear, recognisable label so owners and reviewers find it. |
| Owner | Accountability. Every AI system should have a named owner. |
| Description | What the system does, in plain language. |
| Supplier / vendor | Whether it is internal, vendor-provided or a hybrid. |
| Data context | What categories of data the system touches. |
| Lifecycle status | Whether it is proposed, in use, retiring or retired. |
- Open the Registry in your workspace.
- Select Add AI system (or accept a system surfaced by Discovery).
- Enter the name, owner and description.
- Record the supplier, data context and lifecycle status.
- Save. The system now appears in your inventory and is ready for intake.
Good practice
Section titled “Good practice”- One owner, always. Ownership is what makes governance actionable.
- Describe purpose, not implementation. Reviewers care about what it does and why.
- Register early. Capturing a system at proposal stage is far cheaper than reconstructing its history later.
With the system registered, complete intake and set a risk tier, then run your first assessment.