Your team is reviewing whether releases followed its own change policy. Most records are available, but one pipeline result is missing and an exception is still open. A report can help you see which requirements the records support and where you need to follow up.
Give the report a specific scope
For this example, replace the original prompt's standard placeholder with our team release-control policy, the period with September 1–30, and the scope with the checkout service. The sample uses a fictional team policy, so its conclusions apply to that policy alone.
The original prompt addresses @security_analyst, so you'll need a conversation where that agent is available to use the mention. You'll supply the records as context; the sample below doesn't install the agent or connect it to your own records.
Include these policy requirements and sample records in your conversation:
Team release-control policy:
- A reviewer other than the author approves the final revision before release.
- The release pipeline passes for that same revision.
- Any exception records an owner, reason, and expiry date.
September records for the checkout service:
- Release R101, revision a11: reviewer Sam approved the final revision;
author Jo; pipeline 501 passed for a11 before release; no exception.
- Release R102, revision b22: reviewer Jo approved the final revision;
author Sam; the pipeline result hasn't been supplied; no exception recorded.
- Release R103, revision c33: reviewer Sam approved the final revision;
author Jo; pipeline 503 failed for c33. Exception E7 permits this release
because the failed check covers a disabled integration. Owner: Alex.
Expires October 7. The follow-up fix is still open.
Look for the distinction between a failure and a gap
The report should make these differences easy to find:
| Release | What can be concluded from the supplied records? | What remains to do? |
|---|---|---|
R101 |
The supplied approval and pipeline records meet the stated requirements. | Nothing further is identified in these sample records. |
R102 |
Independent approval is recorded, but the pipeline requirement can't be assessed. | Find the result for revision b22; don't substitute a passing run for another revision. |
R103 |
The pipeline failed. A documented exception allowed the release, and the fix remains open. | Follow up with Alex before the exception expires. |
For R102, the pipeline outcome remains unknown until you find the missing record. For R103, the failed result and the exception both belong in the report: the exception allowed the release while the fix remained open. If Duo combines those situations into a single “compliant” label, ask it to show the approval, pipeline result, and exception separately so reviewers can follow what happened.
Fill the gap and compare the revision
Try adding this information:
I found pipeline 502. It passed for revision b22 before R102 was released.
Update the report and explain which conclusion changes. E7 is still open.
With a passing pipeline for the released revision, the records now support the pipeline requirement for R102. The report should still show the failed pipeline for R103 and the open exception E7. In your own report, links to the actual approval, pipeline, and exception records let reviewers follow the same reasoning.