Dispatch KB Migration Plan
Dispatch KB Migration Plan
Section titled “Dispatch KB Migration Plan”This page defines the migration approach only. No Dispatch KB content should be copied during this scaffold pass.
Current system split
Section titled “Current system split”- Dispatch KB stays in place for internal ops notes, temporary runbooks, investigations, and coordination context
- This GitHub docs repo becomes the source of truth for public, product, and developer documentation
Future migration classification
Section titled “Future migration classification”Every KB item reviewed for migration should be classified as one of:
- public docs candidate
- internal-only
- stale/archive
- needs rewrite
Guardrails
Section titled “Guardrails”- No KB content should be copied in this first scaffold pass
- Any migration requires explicit review before publish
- Internal-only operational content should remain in Dispatch KB unless Kyle approves a public rewrite
- Content that is stale or unclear should be rewritten instead of copied forward verbatim
Recommended future workflow
Section titled “Recommended future workflow”- Inventory KB articles
- Classify each article
- Rewrite public-facing content into MDX
- Review with the appropriate team members
- Publish only after approval
Review expectations
Section titled “Review expectations”- Jenny can review tone and audience fit for user-facing docs
- Atlas can review structure and long-term docs governance
- Reese can audit migration scope and publish safety before content goes live