chore: checkpoint hermes-generated ops skills

docs/releases/2.0.0-preview/article-outline.md

@@ -0,0 +1,57 @@
+# Article Outline - ECC 2.0 Preview
+
+## Working Title
+
+How I Turned ECC Into an Operator System With Hermes
+
+## Core Argument
+
+Most people treat AI coding tools like isolated chat products.
+
+The leverage comes when you treat the harness, workflow surface, and operator stack as a system:
+
+- reusable skills
+- stable hooks
+- MCP-backed tools
+- cron/accountability loops
+- one operator shell tying the pieces together
+
+## Structure
+
+### 1. The Problem
+
+- too many tools
+- too much context switching
+- too many workflows stuck in personal muscle memory
+
+### 2. What ECC Already Solved
+
+- reusable skills
+- cross-harness portability
+- hook discipline
+- verification and security patterns
+
+### 3. Why Hermes Was the Missing Layer
+
+- chat + TUI + cron + workspace memory
+- business and content ops live next to engineering
+- terminal-native operator flow instead of app sprawl
+
+### 4. What Ships in the Public Preview
+
+- sanitized Hermes setup guide
+- generated workflow skills
+- release and distribution collateral
+- cross-harness 2.0 positioning
+
+### 5. What Is Still Private or Still Coming
+
+- secrets and auth
+- personal datasets
+- some operator-specific automation packs
+- deeper CRM/finance/Google Workspace integrations
+
+### 6. Closing Point
+
+The goal is not “use my exact stack.”
+The goal is to build an operator system that compounds.