DocuGardenerDocs

Triage Inbox

Your central queue for reviewing and resolving documentation drift findings.

What Is the Triage Inbox?

The Triage Inbox is a prioritised list of all unresolved drift findings across your monitored repositories. Every time DocuGardener analyses a pull request and finds documentation drift above the threshold, a finding appears here. Think of it as a to-do list for your documentation health.

Each item in the inbox shows the repository name, PR title, drift score, affected files, and the current status.

Status Chips

Every finding has a status chip indicating where it is in the resolution workflow:

StatusMeaning
Review requiredThe finding is new and needs human review. No action has been taken yet.
AI workingDocuGardener is generating a fix PR. This typically takes 30 -- 60 seconds.
Fix readyA fix PR has been created and is ready for review or has been auto-merged.

Available Actions

Click on any finding to open the detail panel. From there you can take one of the following actions:

Apply Fix

DocuGardener generates exact Markdown diffs for the affected files. Click Apply fix to have DocuGardener open a pull request with the suggested documentation changes. The PR is linked back to the original finding for traceability.

Dismiss with Reason

If a finding is a false positive or not relevant, dismiss it with a reason. Dismissed findings are removed from the inbox but remain in the audit log. Common dismiss reasons include “false positive”, “intentional divergence”, and “will fix later.”

Mark No Update Needed

If the documentation is actually correct and the drift score is misleading, mark the finding as “no update needed.” This teaches DocuGardener about your documentation conventions over time.

Bulk Actions

Select multiple findings using the checkboxes on the left side of each row, then use the bulk action bar that appears at the top of the list. You can bulk dismiss or bulk mark as “no update needed.”

Filters

The inbox supports several filters to help you focus on what matters:

FilterDescription
RepositoryShow findings from a specific repository only.
SeverityFilter by drift score range (low, medium, high).
StatusShow only findings with a specific status (Review required, AI working, Fix ready).

Policy Violations

If you have documentation policies configured, violations appear alongside drift findings in the inbox. Policy violations are visually distinct — they show the policy name and a description of what was violated. Resolution options are the same: apply a fix, dismiss, or mark as acceptable.

Tip:Policy violations have a “Policy next steps” panel in the detail view that explains exactly what needs to change to satisfy the policy.