What the registry tracks
Why this matters
Governance, compliance, and ROI calculations all need the registry as the inventory of record: If a model isn’t in the registry, it doesn’t show up in any of the downstream views. The first job of a new Observatory org is usually populating the registry.Populating the registry
Three ways:From telemetry
Models that show up in runs are auto-registered. You confirm and fill in metadata.
Manual entry
Add a model that isn’t running yet (preview, eval, planned).
Import
Bulk import from CSV or from FlowX AI Platform’s agent definitions.
API
Programmatic registration through
POST /api/registry/models.Risk tiering
The default tiers map roughly to the EU AI Act risk pyramid:
Tiering can be manual or computed. Computed tiering uses data tags and capability flags (e.g. “makes decisions about people” + “trained on personal data” → High).
API
Related resources
Risk Dashboard
Where data and model tags become risk scores.
Compliance
Risk tier drives which frameworks apply.