Documentation Governance

Document Metadata

• Document ID: WSAI_OperationsManual_v1_DOC_002
• Status: ACTIVE
• Authority: WSAI_DocumentationGovernance_v1
• Operations Manual Revision: 1.1
• Classification: Internal, Private, Operational Authority
• Publication Target: wickedspooky.org
• Public Availability: NOT PERMITTED

Purpose

This document establishes the governance standards for all operational documentation within the Wicked Spooky Enterprise ecosystem.

It defines documentation authority, publication layers, document lifecycle, artifact preservation, media standards, derivative publication rules, and institutional memory standards.

Documentation Philosophy

Documentation is not a byproduct of operations. Documentation is part of operations.

The purpose of documentation is to preserve truth, knowledge, context, decisions, and experience.

Documentation Authority

The authoritative repository for operational documentation is wickedspooky.org.

Classification: Private, operator access only, non-indexed, non-public.

Operational Truth Originates Here.

Publication Layer Governance

Layer 1: Operational Authority Layer

Location: wickedspooky.org

Purpose: Authoritative documentation, operations manual, runbooks, architecture, validation procedures, registry documentation, and recovery procedures.

Rule: Source of truth.

Layer 2: Public Technical Layer

Location: wickedspookyit.com

Purpose: Technical articles, engineering commentary, case studies, and implementation guidance.

Rule: Derived content only. Content must be sanitized.

Layer 3: Commercial Knowledge Layer

Location: wickedspooky.ai

Purpose: Courses, frameworks, templates, knowledge products, and membership content.

Rule: Commercial derivatives.

Documentation Derivation Rule

Approved flow:

Operational Documentation
        ↓
Technical Article
        ↓
Knowledge Product

Disallowed flow:

Marketing Content
        ↓
Operational Documentation

Operational truth must never originate from marketing materials.

Document Lifecycle

Draft
    ↓
Validated
    ↓
Artifact Locked
    ↓
Bootstrap Package
    ↓
Published
    ↓
Governed

Documents are not considered complete until an artifact exists, a bootstrap package exists, and a published version exists.

Documentation Preservation Requirements

Every approved document must exist in artifact form, published form, and recovery form.

Media Standards

Authority: WSAI_DocumentationMediaStandards_v1

Required: Architecture diagrams and workflow diagrams.

Approved: Hero images, technical illustrations, Crisis Cat callouts, and visual taxonomy.

Visual Taxonomy

Authority: WSAI_VisualTaxonomyRegistry_v1

• The Codex = Operations Manual
• The Vault = MariaDB Authority
• The Archive = Operational Registry
• The Messengers = Make Automation
• The Reading Room = WordPress Presentation
• The Watchtowers = Validation Gates
• The Recovery Library = Bootstrap Packages

Technical names remain authoritative. Visual names enhance documentation.

Crisis Cat Wisdom Governance

Authority: WSAI_CrisisCatWisdom_v1

Purpose: preserve lessons learned, operational experience, governance decisions, and institutional memory.

Documentation Quality Standards

Documentation must be accurate, current, governed, recoverable, searchable, versioned, portable, and AI-ingestible.

Crisis Cat Guidance

🐾 Crisis Cat Says
If it isn't documented, it doesn't exist.

Related Documents

• Platform Overview
• Operational Authority Model
• Enterprise Architecture
• Documentation Media Standards
• Visual Taxonomy Registry
• Crisis Cat Wisdom Guide