Key concepts, in plain English
The architecture page shows the four doors. These are the words they share. A term means the same thing at every door, because every door is generated from the same ontology.
| Term | What it means |
|---|---|
| Taxonomy | A framework’s catalogue of risks and controls (for example NIST AI RMF, FINOS AIGF) |
| Risk | A named, identified harm (for example atlas-toxic-output, nist-confabulation) |
| Control / Action | Something you do or deploy to detect or mitigate a risk |
| Obligation | A requirement a framework imposes, with evidence categories describing how you prove it |
| Crosswalk | A machine-generated mapping of equivalent concepts between frameworks |
| Incident | A realised risk, something that happened (for example ibm-risk-atlas-ri-fake-legal-cases), linked back to the risks it demonstrates |
| Evaluation | A benchmark or test that measures a risk or a capability (for example ai_eval_PopQA), linked to the datasets and tasks it uses |
| BYOD | Bring Your Own Data: your internal policies encoded in the same schema, queryable alongside the open data |
Each entity type has its own CLI command, and cli-examples.md lists them all. working-with-the-data.md says how to add your own records under these terms.