Scheduled audits

Webhooks only cover changes DraftStack sees. A missed delivery, a repository added late, or an expired backfill window leaves docs drift that no event reports.

Scheduled audits close that gap. When audits are enabled for a project, DraftStack sweeps each monitored repository once a day, collects the default-branch commits since the last sweep, and runs them through the same analysis, generation, and review pipeline as a merged pull request.

Audit suggestions appear in the inbox with an Audit: title and a compare link for the commit window. The project confidence threshold and publish mode apply unchanged.

Auto-approval

Projects can also set an auto-approval threshold. Suggestions whose confidence meets or exceeds it publish immediately under the project’s publish mode, with no human reviewer: combined with publish mode auto, the loop repairs docs end to end on its own. A publish failure leaves the suggestion pending for normal review. Auto-approval is off until a threshold is set, and reviewers can read every automatic publication in the activity log.

Learning from dismissals

Each sweep also reads dismissal reasons recorded since the last audit and converts substantive ones into suggested project knowledge rules. The rules stay disabled for prompts until a reviewer confirms them, so the pipeline learns from rejections without acting on unreviewed feedback.

Audits are off by default. Enable them per project in settings or through the API with auditEnabled: true.