Traceability
Traceability is the ability to follow an artifact, data, result, or decision through its origins, relationships, transformations, and relevant history.
Machine Learning Platform Engineering
Traceability is the ability to follow an artifact or result back to its originating inputs, configurations, and processing steps.
- How it is used
- Supports production ML training, evaluation, deployment, observability, and repeatable delivery.
- How deep it goes
- Descends from rationale into MLflow logging, run-based validation, registry lineage, promotion gates, aliases, and rollback.
- Examples
- Uses MLflow runs, recommender metrics, model signatures, dashboards, registered aliases, staging promotion, and rollback.
- What you can do after
- Operate/configure MLflow workflows that retrieve, validate, promote, document, and roll back models using recorded lineage.
Read how Machine Learning Platform Engineering explains traceability →
GitHub Actions in Action: Continuous integration and delivery for DevOps
Traceability is the ability to associate a software change with its originating requirement, request, review, and deployment evidence.
- How it is used
- Establishes auditable links from software changes and deployments to identities, requirements, reviews, and compliance evidence.
- How deep it goes
- Explains Git history, enterprise identity controls, signed-commit setup, branch policies, and deployment-to-requirement tracing.
- Examples
- Uses GPG commit-signing commands and a deployment view that traces a release tag through a pull request to an issue.
- What you can do after
- Operate/configure it by enforcing signed commits, identity linkage, review policies, and deployment records for end-to-end traceability.
Related concepts
- AI-specific governanceused by · AI governance is the set of policies, processes, controls, and oversight mechanisms for directing and managing the development and use of artificial-intelligence systems.
- gitused by · Git is a distributed version-control system that records changes to files and supports managing project history and collaboration across repositories.
- single sign-onconfigured by · Single sign-on is an authentication arrangement in which one authentication event enables a user to access multiple applications or services without signing in separately to each.
- approval decisionproduced by · An approval decision is an explicit authorization or acceptance by an authorized person or system that allows a proposed action, change, or item to proceed.
- signed commitconfigured by · A signed commit is a source-control commit accompanied by a cryptographic signature verifiable with the signer's public key.
- responsibilityaddresses · A responsibility is a duty, capability, or area of accountability assigned to a person, role, class, object, or other entity.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.