Provenance is the evidence trail that records where an artifact came from, how it moved or changed, which tools and constraints shaped it, and who approved the result. For AI-assisted delivery, “the developer clicked approve” is not an audit trail: reliable governance needs observable lineage. section 5.5.2
A useful provenance record captures:
- The model used, tools called, files modified, and amount of code produced or transformed by AI. section 5.5.2
- Checks performed, human approvals, applicable repository policies, and verification evidence for sensitive or critical paths. section 5.5.2
- The origin and credibility of proposed dependencies, including registry existence, maintenance history, and suspicious naming. section 5.2.4
From approval gesture to reconstructable change
When an AI-assisted change introduces a defect, provenance lets a team ask what context the agent saw, what actions it took, which checks ran, and where the decision failed. The same principle can block a hallucinated package before installation by validating its registry presence and maintainers. section 5.5.2 section 5.2.4

















