Core Workflow
AI Author Mode
The documentation safety net for AI-native teams. Detects PRs authored by Copilot, Cursor, Devin, or Claude via four independent signals — then opens and merges the documentation fix automatically when CI passes.
- ✓Detects: bot sender · branch prefix · PR body marker · custom pattern
- ✓Auto-merges via squash, merge commit, or rebase — your choice
- ✓AI Authorship Signal row in every fix PR for full traceability
PR Drift Detection
Every pull request triggers a full documentation analysis. DocuGardener compares semantic meaning of code and docs to catch inconsistencies before they merge.
- ✓Semantic diff across code and Markdown
- ✓Drift score 0–100 with per-file breakdown
- ✓GitHub check run integration
Auto-Fix Suggestions
Instead of flagging a problem and leaving, DocuGardener generates the exact Markdown update — apply as a GitHub suggestion or let it open an auto-fix PR.
- ✓Precise Markdown diff, not generic advice
- ✓Apply as GitHub suggestion in one click
- ✓Auto-fix PR opens for team review
Pre-Push Drift Check
Catch documentation drift before it even reaches CI. The VS Code extension calls a stateless /check endpoint on every pre-push hook, so developers get feedback in their IDE.
- ✓Zero-latency local feedback loop
- ✓Suggested docs open directly in editor
- ✓Policy violation diagnostics in Problems panel
Triage Inbox
A Linear-style queue for all unresolved drift findings across your connected repositories. Review, dismiss with reason, bulk-approve, or escalate — without leaving DocuGardener.
- ✓Chronological drift queue
- ✓Dismiss with mandatory reason (configurable)
- ✓Bulk actions for large backlogs
Nightly Rollup Reports
End-of-day summary delivered to Slack or email. Shows drift score delta, PRs scanned, and top unresolved findings — keeping the team informed without opening a dashboard.
- ✓Slack and email delivery
- ✓Drift score trend over 7 / 30 days
- ✓Top affected repos highlighted
Governance & Compliance
Documentation Policy Enforcement
Define documentation obligations as code. YAML rules specify which file paths require which docs, with advisory, blocking, or blocking-with-reason enforcement levels.
- ✓Path-based require_docs rules in .github/docugardener.yml
- ✓Advisory, blocking, or blocking-with-reason enforcement
- ✓Audit-logged when policy violations are dismissed
Risk Zone Dashboard
Management-facing view of documentation risk concentration across your fleet. See which repos and doc types carry the highest unresolved drift — and drill into the findings.
- ✓Repo vitality index with drill-down to open drift
- ✓Filter by repo, doc type, and time range
- ✓Single health score for executive reporting
Audit Log
Every security-relevant action is recorded with a tamper-evident SHA-256 hash chain. CSV / JSON evidence export for compliance packages available on Team.
- ✓SHA-256 hash chain — every record verifiable
- ✓18 event types across login, triage, settings, and role changes
- ✓Exportable CSV / JSON with date-range filters
RBAC
Four built-in roles — Admin, Member, Auditor, and Billing Admin. Admins manage repos and team. Auditors get read-only access to the audit log.
- ✓Admin · Member · Auditor · Billing Admin
- ✓Invite by email from the Settings page
- ✓Role changes audit-logged
SSO & SCIM Provisioning
Enterprise identity integration via SAML SSO and SCIM 2.0. Automate user provisioning and deprovisioning from your identity provider.
- ✓SAML SSO login
- ✓SCIM 2.0 user lifecycle management
- ✓Central session revocation
Evidence Export
Export the complete audit log as CSV or JSON for a specified date range and event filter. Rate-limited and access-controlled for compliance packages.
- ✓Date range + event type filters
- ✓CSV and JSON formats
- ✓Rate-limited to prevent abuse
Fleet Analytics
Aggregate documentation health across all connected repositories. Track drift score trends, PR analysis counts, and per-repo health over time.
- ✓Fleet health score across all repos
- ✓PR analysis volume over time
- ✓Per-repo drift score breakdown
BYOK & Local Models
Four deployment modes to fit your data residency and security posture — from fully managed to fully air-gapped.
- ✓Platform · BYOK Cloud · BYOK Local · Sovereign
- ✓BYOK Local and Sovereign: zero data leaves your network
- ✓Exportable environment profile for security review
More Capabilities
Cross-Vendor Agent Instructions
Keep every AI coding agent aligned with your documentation policy — automatically. DocuGardener compiles your policy into native instruction files for 4 agent ecosystems.
- ✓AGENTS.md · copilot-instructions.md · cursor rules · CLAUDE.md
- ✓Nightly staleness check — one-click Propose opens the update PR
- ✓Preview compiled output inline before proposing
Cross-Repo Drift Detection
Fan-out across sibling repos — detects when a code change breaks docs in related repos. Findings appear inline in the PR comment and the Triage Inbox.
- ✓Fan-out analysis across up to 3 (Team) or 10 (Enterprise) siblings
- ✓Prompt injection defence on all cross-repo LLM calls
- ✓Configurable per-repo via Settings → Repositories
Slack Integration
Post drift alerts, nightly rollups, and triage updates to any Slack channel. Configure per-repo channel routing from the Settings page.
- ✓Per-repo Slack channel routing
- ✓Drift alerts on PR open
- ✓Nightly rollup digest
Jira Integration
Keep your Jira tickets in the loop. DocuGardener posts lifecycle comments on linked tickets when drift is detected, a fix PR is created, or the issue is resolved.
- ✓Auto-comment on linked Jira tickets at 4 lifecycle points
- ✓Works with any ticket key in PR branch, title, or body
- ✓No extra setup — uses your existing Jira workflow