A platform team creates a reusable agentic workflow that triages bugs across five services, needing shared prompts, separate code, and clear ownership so product managers can update instructions safely. Which folder structure best supports this agentic workflow implementation?

The correct structure centralizes shared prompts for reuse across five services while keeping service code in separate directories and mapping ownership in CODEOWNERS so product managers can safely update instructions with required review, which balances reusability, blast-radius isolation, and governance for agentic workflows. The alternative that keeps versioned prompts beside each service codebase with review ownership preserves separation and governance but sacrifices central sharing, leading to duplication, drift, and inconsistent triage behavior as common instructions evolve independently. The alternative that stores shared prompts centrally with separated code but allows edits without reviewers preserves sharing and separation yet removes the safety control, so non-technical updates can ship without approval and break downstream agents. The alternative that hosts shared prompts centrally with unified service logic under clear mapping preserves sharing and ownership but collapses service boundaries, so changes for one service risk regressions in others and independent deployment becomes difficult. On exams, avoid selecting answers that satisfy two of three explicit constraints because distractors are designed to look operationally mature while dropping exactly one keyword from the stem. As a practical check, inspect the repository for a top-level prompts library, distinct service folders, and CODEOWNERS rules requiring owner review on prompt paths before approving the design.