Knowledge rules

Knowledge rules are durable facts about a project that DraftStack includes with every analysis and generation call: which sections are auto-generated, which repository maps to which docs area, what content type lives where, and any custom conventions the team records.

Rules come from three sources:

• Auto-detection: when DraftStack builds the docs manifest, it proposes rules from the navigation structure, path patterns, and OpenAPI configuration.

• Dismissal distillation: scheduled audits convert substantive dismissal reasons into candidate rules, so the pipeline stops repeating mistakes reviewers already rejected.

• Manual entry: teams add custom rules directly in project settings.

Suggested versus enabled

Auto-detected and distilled rules arrive as suggestions and do not influence prompts until a reviewer confirms them. Confirmed rules apply to every later suggestion for the project.

Write rules the way you would brief a new teammate: name the convention, then the reason. Specific rules with concrete examples outperform broad ones.