Unified Sovereign Operations

This skill provides a comprehensive, integrated framework for executing complex sovereign operations. It merges the capabilities of eight specialized skills into a single, cohesive workflow, enabling end-to-end project delivery with a focus on cryptographic integrity, evidence-based decision-making, and autonomous execution.

Core Principles

• Sovereign Forever: Zero SaaS dependency, cryptographic integrity as default.

• Measure Twice, Cut Once: Plan before executing, verify before delivering.

• Assume Nothing, Test Everything: Every claim must be falsifiable and verified.

• Evidence-Grade: All intelligence and artifacts are hashed, timestamped, and auditable.

• Community Authentic: Campaigns and strategies emerge from community needs, not imposed from above.

The Unified Workflow

This unified skill follows a dynamic, six-phase workflow that adapts to the specific needs of the operation. The phases are not strictly linear and can be engaged as required.

• Intelligence & Reconnaissance: Gather, classify, and analyze all source material.

• Strategy & Doctrine: Formulate the strategic plan, define the operational doctrine, and establish the governance framework.

• Architecture & Development: Design and build the required systems, from CI/CD pipelines to constitutional governance platforms.

• Valuation & Analysis: Conduct enterprise valuations, gap analysis, and market survivability assessments.

• Campaign & Deployment: Execute community campaigns, deploy assets, and manage multi-platform outreach.

• Reporting & Reconciliation: Deliver comprehensive reports, presentations, and SITREPs, reconciling all claims against verifiable evidence.

Phase 1: Intelligence & Reconnaissance

This phase integrates the core intelligence-gathering components of the strategic-intelligence-audit , enterprise-valuation , and community-campaign-builder skills.

Key Actions

• Source Ingestion: Extract all data from target websites, documents, media, and community platforms (WhatsApp, Gmail, etc.).

• Classification: Classify every piece of intelligence as COPYABLE , AUTOMATABLE , or ELITE .

• Founder & Corporate Intelligence: Map corporate structures, founder networks, and investor relationships.

• Competitor Analysis: Identify and analyze 3-5 direct competitors.

• Market Sizing: Determine TAM/SAM/SOM with credible, cross-validated sources.

Evidence Management

• All gathered intelligence must be timestamped, hashed (SHA-256), and stored in a version-controlled evidence directory.

Phase 2: Strategy & Doctrine

This phase combines the strategic planning elements of strategic-doctrine-deployment , constitutional-governance-builder , and community-campaign-builder .

Key Actions

• Define Campaign Pillars: Establish 3-5 core themes based on community needs and the candidate's authentic story.

• Formulate Constitutional Framework: Define the invariants, forbidden states, failure policies, and authority ladder for governance systems.

• Create Campaign Blueprint: Generate a comprehensive strategy document with a phased action plan.

• Integrate Doctrine: Copy all strategic documents into the docs/ directory of the target repository.

Phase 3: Architecture & Development

This phase merges the development and deployment workflows of deployment-consolidation , constitutional-governance-builder , and cicd-pipeline-diagnosis .

Key Actions

• Diagnose CI/CD Failures: Run the automated scanner to identify and classify pipeline failure vectors.

• Design Target Architecture: Propose and visualize a robust, 6-stage CI/CD pipeline architecture.

• Consolidate & Organize: Structure the consolidated repository according to best practices.

• Build Deliberation Engine: Create the multi-agent deliberation engine with hash-chained audit trails.

• Implement Design System: Apply the sovereign institutional design system (dark navy, gold/platinum, serif/monospace fonts).

Phase 4: Valuation & Analysis

This phase leverages the enterprise-valuation skill to conduct a full-spectrum financial and strategic analysis.

Key Actions

• Select Valuation Methodology: Choose the appropriate method (Sum-of-the-parts, Revenue Multiple, DCF).

• Generate Financial Models & Charts: Create projections and visualizations based on the gathered intelligence.

• Conduct Gap Analysis: Identify missing pieces in the target's strategy (revenue model, defensibility, unit economics).

• Freestyle Pattern Recognition: Cross-reference all data to find contradictions, hidden connections, and anti-patterns.

Phase 5: Campaign & Deployment

This phase integrates the deployment and outreach components of deployment-consolidation , community-campaign-builder , and strategic-doctrine-deployment .

Key Actions

• Curate Music Assets: Collect and create campaign songs aligned with the defined themes.

• Generate Deployment Scripts: Create the master deployment script and GitHub Actions workflow.

• Initialize Git & Generate Attestations: Create the Git repository and generate cryptographic attestations of the repository state.

• Multi-Platform Deployment: Distribute campaign content across WhatsApp, Suno, Spotify, Facebook, and Twitter/X.

• Sync to Cloud: Sync all artifacts to the corresponding Google Drive folder.

Phase 6: Reporting & Reconciliation

This phase combines the reporting and delivery workflows of all the merged skills, with a strong emphasis on the strategic-intelligence-audit and presentation-workflow methodologies.

Key Actions

• Generate Presentations: Create slide decks and speaker scripts from the strategic documents.

• Formulate Remediation Plan: Draft a detailed, prioritized remediation plan for any identified failures.

• Produce SITREP: Generate a formal Situation Report with an artifact inventory, SWOT analysis, and reconciliation matrix.

• Deliver Final Report: Compile all findings, visualizations, and recommendations into the standard report template.

Reconciliation Protocol

• One working implementation beats 74 documented aspirations. Report what IS, not what SHOULD BE.

• Verify all claims against the actual codebase, test results, and server health.

• Use no absolute language ("perfect," "fully bug-free"). Report the verifiable state only.