A bank builds an AI-assisted interest-calculation module. In Business, an analyst declares the calculation rule and its acceptance criteria; a separate reviewer approves them. In Architecture, the calculation library is pinned to an approved version. Development generates the code, and the Analyzer's Quality Gate rejects an unsanctioned dependency at the source. A compliance officer — distinct from both the author and the developer — signs off.
Months later, an external auditor asks: who changed this rate logic, when, and on whose authority? The Analyzer answers with a single timestamped chain — requirement → architecture → code → three named approvers. There is no archaeology across tickets and commits. The SOX change-management and segregation-of-duties evidence is the development trail.
