This reference defines the canonical document types used throughout the centrexIT Knowledge Center. Each type maps to a directory, a docType frontmatter value, and a specific purpose.

• Directory: policies/
• docType: policy
• Purpose: Governance rules, mandates, and compliance requirements
• When to use: The article defines what must be done, sets organizational rules, or establishes compliance boundaries
• Signals: “policy”, “compliance”, “enforcement”, “shall”, “must”
• Example: Operating Policies, Password Policy, Backup Policy

• Directory: standards/
• docType: standard
• Purpose: Configuration baselines, requirements, CMDB definitions, and technical specifications
• When to use: The article defines what something should be — a baseline, naming convention, configuration requirement, or specification
• Signals: “standard”, “baseline”, “configuration”, “requirement”, “specification”
• Example: Firewall Standard, CMDB CI Standard, Acceptable Use Standard

• Directory: processes/
• docType: process
• Purpose: High-level workflows with phases, KPIs, inputs/outputs, and cross-team coordination
• When to use: The article describes an end-to-end workflow at a strategic level, with named phases, metrics, and ownership
• Signals: “process flow”, “phase”, “KPI”, “input/output”, “metric”
• Example: Change Enablement, Procurement and Vendor Management, Process Design

• Directory: procedures/
• docType: procedure
• Purpose: Step-by-step operational processes for escalation, incident response, patching, and more
• When to use: The article describes a multi-step operational process involving roles, escalation paths, or cross-team handoffs
• Signals: “workflow”, “escalation”, “roles and responsibilities”, “SLA”
• Example: After-Hours Support Workflow, Sprint Retro, Critical Incident Response

• Directory: work-instructions/
• docType: work-instruction
• Purpose: Granular, click-by-click task instructions for completing a specific action
• When to use: The article answers “How do I do X?” with numbered steps, screenshots, and specific UI navigation
• Signals: “step 1”, numbered lists, “click”, “navigate”, “select”, “enter”
• Example: Reset User Password, Create NRFC, Configure VPN Client

• Directory: reference/
• docType: reference
• Purpose: Static information, contacts, lookup tables, vendor details, and environment documentation
• When to use: The article provides information to look up rather than steps to follow
• Signals: “reference”, “contact”, “vendor”, “inventory”, “lookup”, “environment”
• Example: Service Provider Matrix, Site POCs, Category Definitions

• Directory: manuals/
• docType: manual
• Purpose: Comprehensive guides covering broad topics such as onboarding, platform administration, or service delivery
• When to use: The article is a multi-chapter or multi-section guide that covers a broad topic comprehensively
• Signals: “manual”, “chapter”, “guide”, “handbook”
• Example: New User Whitelist Instructions (comprehensive guide with multiple sections)

Directory	docType	Label
policies/	policy	Policies
standards/	standard	Standards
processes/	process	Processes
procedures/	procedure	Procedures
work-instructions/	work-instruction	Work Instructions
reference/	reference	Reference
manuals/	manual	Manuals

When classifying an article, apply these rules in order:

1. Filename prefix (highest confidence): ST- = standard, POL- = policy, PR- = process, CORE- = procedure, WI- = work instruction, 3P- = reference
2. Content signal scoring: Match keywords and patterns against the article body
3. Structural heuristics: Numbered steps suggest work instruction; escalation content suggests procedure; contact/POC content suggests reference