Skip to main content

Versioning & Content Maintenance

1. The "Rot" Problem​

Content rots. Processes change. If the KB is wrong, trust is lost. Maintenance is not optional; it is scheduled.

2. Version Control Policy​

  • v1.0: Major Release (New Concept).
  • v1.1: Minor Update (Clarification, Typo).
  • v2.0: Significant Change (Process/Logic shift). Requires Notification.

3. The Audit Cadence​

  • Tool: Automated SEO crawler or Manual check.
  • Action: Fix 404s in the Public KB.

Quarterly: "Truth" Audit​

  • Process:
    • Export list of all Live AKUsAKU A standardized, independent, and reusable piece of knowledge (concept, procedure, script, etc.) that acts as the fundamental building block of the Content Engine..
    • Sort by "Last Updated."
    • Any AKUAKU A standardized, independent, and reusable piece of knowledge (concept, procedure, script, etc.) that acts as the fundamental building block of the Content Engine. older than 6 months is flagged Needs Review.
  • Owner: Assigned SMESME An individual with deep understanding and authority on a specific process, topic, or technology. must verify: "Is this still true?"
    • Yes: Update date.
    • No: Edit or Deprecate.

Yearly: "Purge"​

  • Action: Archive AKUsAKU A standardized, independent, and reusable piece of knowledge (concept, procedure, script, etc.) that acts as the fundamental building block of the Content Engine. that haven't been viewed/used in 12 months.
  • Status: Change to Archived. Remove from active search index.

4. Deprecation Protocol​

When an AKUAKU A standardized, independent, and reusable piece of knowledge (concept, procedure, script, etc.) that acts as the fundamental building block of the Content Engine. is retired:

  1. Mark Status: Deprecated.
  2. Add Banner: "⚠️ This process is no longer in use. See [New Link]."
  3. Redirect: Set up 301 Redirect on the Public KB to the new version.
  4. Notify: Inform Support Team via Slack.

Related Documents: