<aside> 🔗 This page answers the auditor question: 'Why does this line of code exist? Who decided it? Which prompt produced it? Was it aligned with the original business requirement?' In D-POAF, the answer is always reachable in under 5 minutes.
</aside>
Every artifact produced by D-POAF must trace back to a clear business intent. Here is the chain, top to bottom:
Production artifact (code, document, decision)
↑
│ [AI:model:PA-ID] tag in commit message (DL-005)
│
Pull Request / Commit (Git history)
↑
│ Linked PR URL in PA page
│
Prompt Action (PA-NNN)
↑
│ Model + Config + Context (Traceability Thread, DL-006)
│ Wave relation field (link to parent Wave Scope)
│
Wave Scope (WAVE-YYYY-NNN)
↑
│ Business Objective + PoD/PoV/PoR criteria
│ Linked Jira Epic (DL-004)
│
Business Intent (Sponsor's request)
Use case: 'Where did the AI generate code for our sentiment classifier?'
Time to answer: 2-3 minutes.
Use case: 'Why is this line of code in the codebase? Who wrote it? With what intent?'
git blame on the suspicious line