Operational Authority Model

Document Metadata

Document ID: WSAI_OperationsManual_v1_DOC_003
Status: ACTIVE
Authority: WSAI_OperationsManual_v1
Classification: Internal, Private, Operational Authority
Publication Target: wickedspooky.org
Last Validation: 2026-05-31

Purpose

The Operational Authority Model defines how truth is established, maintained, promoted, consumed, and validated throughout the Wicked Spooky Enterprise ecosystem.

This document is the foundational governance document for all enterprise systems.

Core Principle

Operational Truth Must Have Exactly One Authority.

If multiple systems become authoritative for the same operational fact, drift occurs, trust declines, recovery becomes difficult, and governance breaks down.

Enterprise Authority Hierarchy

MariaDB
        ↓
Make
        ↓
WordPress
        ↓
Runtime Systems

Tier 1: The Vault

Technical Name: MariaDB

Role: Operational Authority

Responsibilities: Governed data, registry information, workflow state, validation status, configuration governance, and operational memory.

Rule: Truth lives here.

Tier 2: The Messengers

Technical Name: Make

Role: Orchestration Layer

Responsibilities: Workflow execution, automation, synchronization, notifications, publishing, and data movement.

Rule: Make executes truth. Make does not own truth.

Tier 3: The Reading Room

Technical Name: WordPress

Role: Presentation Layer

Responsibilities: Documentation, publishing, public presentation, and knowledge delivery.

Rule: WordPress presents truth. WordPress does not define truth.

Tier 4: Runtime Infrastructure

Technical Name: Servers, applications, and services.

Role: Deployed state.

Rule: Runtime state must match governance.

Promotion Model

Operational truth flows downward:

Governance
        ↓
Authority
        ↓
Automation
        ↓
Presentation
        ↓
Runtime

Truth never flows upward.

Disallowed Authority Models

Runtime becoming authority
WordPress becoming authority
Make becoming authority

These patterns create drift.

Validation Gates

Visual Name: The Watchtowers

Purpose: Verify runtime matches authority.

Documentation Authority

The authoritative documentation repository is wickedspooky.org.

Rule: Documentation authority exists outside conversation history.

Artifact Authority

Authoritative artifacts are preserved through bootstrap packages.

Visual Name: The Recovery Library.

Operational Wisdom Authority

Authority: WSAI_CrisisCatWisdom_v1

Rule: Experience must be preserved alongside documentation.

Authority Conflict Resolution

If two systems disagree, the authority hierarchy determines truth.

If WordPress disagrees with MariaDB, MariaDB wins.
If Make disagrees with MariaDB, MariaDB wins.
If runtime disagrees with MariaDB, MariaDB wins.

Always.

Crisis Cat Guidance

🐾 Crisis Cat Says
Operational truth should have exactly one authority.

WSAI Operational Guides

Guides