zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-29 21:43:29 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(ecc2): finalize rc1 release surface

Browse Source
This commit is contained in:
Affaan Mustafa
2026-04-28 22:10:04 -04:00
parent 4e66b2882d
commit 0a87323eda
40 changed files with 863 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
docs/releases/2.0.0-rc.1/article-outline.md Normal file
View File

@@ -0,0 +1,61 @@
# Article Outline - ECC v2.0.0-rc.1
## Working Title
Turning ECC Into a Cross-Harness Operator System
## Core Argument
Most agentic work breaks down because the tools stay isolated.
The leverage comes from treating the harness, reusable workflow layer, and operator shell as one system:
- skills for repeatable work
- hooks and tests for enforcement
- MCPs for tool access
- memory and handoffs for continuity
- one operator shell that can route daily execution
## Structure
### 1. The Problem
- too many chat windows
- too many tool-specific workflows
- too much context living in personal habit instead of reusable system shape
### 2. What ECC Already Solved
- reusable skill format
- cross-harness install surfaces
- hooks and verification discipline
- security and review patterns
- operator workflow skills around content, research, and business ops
### 3. Why Hermes Is the Operator Layer
- chat, CLI, TUI, cron, and handoffs can sit above the reusable ECC layer
- business and content work can run next to engineering work
- the daily loop becomes easier to inspect and improve
### 4. What Ships in rc.1
- sanitized Hermes setup guide
- release and distribution collateral
- cross-harness architecture doc
- Hermes import guidance
- clearer 2.0 positioning in the repo
### 5. What Stays Local
- secrets and auth
- raw workspace exports
- personal datasets
- operator-specific automations that have not been sanitized
- deeper CRM, finance, and Google Workspace playbooks
### 6. Closing Point
The goal is not to copy one exact stack.
The goal is to build an operator system that turns repeated work into reusable, measurable surfaces.

42
docs/releases/2.0.0-rc.1/demo-prompts.md Normal file
View File

@@ -0,0 +1,42 @@
# Hermes x ECC Demo Prompts
## Prompt 1: ECC Builds ECC
Use the current ECC repo and the public release pack at `docs/releases/2.0.0-rc.1/`.
Do 4 things in order:
1. Inspect git status and the current repo diff, then give me a concise ECC v2.0.0-rc.1 PR or release summary that proves ECC is being used to build ECC itself.
2. Finalize one strong X thread.
3. Finalize one strong LinkedIn post.
4. Tell me the exact 3 recordings I should do next plus what Hermes can generate automatically after I record.
Keep it decisive and practical.
## Prompt 2: Turn Recording Into Assets
Assume I just recorded:
- one face-camera hook
- one screen capture of Hermes using ECC to ship ECC v2.0.0-rc.1
- one setup walkthrough of the Hermes x ECC workspace
Give me:
1. a short-form edit plan for X, LinkedIn, TikTok, and YouTube Shorts
2. a voiceover script if I want to re-record clean audio
3. the exact repo-relative filenames and folders I should use for raw footage
4. the assets Hermes can generate automatically after I drop the files in place
Keep it operational.
## Prompt 3: Public Launch Push
Using the ECC v2.0.0-rc.1 release pack, give me:
1. one release tweet
2. one follow-up tweet
3. one LinkedIn comment I can paste under the post
4. one short Telegram handoff I can send to Hermes later to keep distributing this launch across channels
Make it sound like an operator shipping real work, not a launch thread cliche.

41
docs/releases/2.0.0-rc.1/launch-checklist.md Normal file
View File

@@ -0,0 +1,41 @@
# ECC v2.0.0-rc.1 Launch Checklist
## Repo
- verify local `main` is synced to `origin/main`
- verify `docs/HERMES-SETUP.md` is present
- verify `docs/architecture/cross-harness.md` is present
- verify this release directory is committed
- keep private tokens, personal docs, and raw workspace exports out of the repo
## Release Surface
- confirm package and plugin version policy for `2.0.0-rc.1` (drafted in manifest bump prep)
- confirm whether `ecc2/Cargo.toml` moves from `0.1.0` to `2.0.0-rc.1`
- update release metadata in one dedicated release-version PR
- run the root test suite
- run `cd ecc2 && cargo test`
## Content
- publish the X thread from `x-thread.md`
- publish the LinkedIn draft from `linkedin-post.md`
- use `article-outline.md` for the longer writeup
- record one 30-60 second proof-of-work clip
## Demo Asset Suggestions
- Hermes plus ECC side by side
- release docs being generated or reviewed from the repo
- a workflow moving from brief to post to checklist
- `ecc2/` dashboard or session surface with alpha framing
## Messaging
Use language like:
- "release candidate"
- "sanitized operator stack"
- "cross-harness operating system for agentic work"
- "ECC is the reusable substrate; Hermes is the operator shell"
- "private/local integrations land after sanitization"

28
docs/releases/2.0.0-rc.1/linkedin-post.md Normal file
View File

@@ -0,0 +1,28 @@
# LinkedIn Draft - ECC v2.0.0-rc.1
ECC v2.0.0-rc.1 is live as the first release-candidate pass at the 2.0 direction.
The practical shift is simple: ECC is no longer framed as only a Claude Code plugin or config bundle.
It is becoming a cross-harness operating system for agentic work:
- reusable skills instead of one-off prompts
- hooks and tests instead of manual discipline
- MCP-backed access to docs, code, browser automation, and research
- Codex, OpenCode, Cursor, Gemini, and Claude Code surfaces that share the same core workflow layer
- Hermes as the operator shell for chat, cron, handoffs, and daily work routing
For this release-candidate surface, I kept the repo honest.
I did not publish private workspace state. I shipped the reusable layer:
- sanitized Hermes setup documentation
- release notes and launch collateral
- cross-harness architecture notes
- Hermes import guidance for turning local operator patterns into public ECC skills
The leverage is not just better prompting.
It is reducing the number of isolated surfaces, turning repeated workflows into reusable skills, and making the operating system around the agent measurable.
There is still more to harden before GA, especially around packaging, installers, and the `ecc2/` control plane. But rc.1 is enough to show the shape clearly.

54
docs/releases/2.0.0-rc.1/release-notes.md Normal file
View File

@@ -0,0 +1,54 @@
# ECC v2.0.0-rc.1 Release Notes
## Positioning
ECC v2.0.0-rc.1 is the first release-candidate surface for ECC as a cross-harness operating system for agentic work.
Claude Code remains a core target. Codex, OpenCode, Cursor, Gemini, and other harnesses are treated as execution surfaces that can share the same skills, rules, MCP conventions, and operator workflows. ECC is the reusable substrate; Hermes is documented as the operator shell that can sit on top of that layer.
## What Changed
- Added the sanitized Hermes setup guide to the public release story.
- Added launch collateral in-repo so the release can ship from one reviewed surface.
- Clarified the split between ECC as the reusable substrate and Hermes as the operator shell.
- Documented the cross-harness portability model for skills, hooks, MCPs, rules, and instructions.
- Added a Hermes import playbook for turning local operator patterns into publishable ECC skills.
## Why This Matters
ECC is no longer only a Claude Code plugin or config bundle.
The system now has a clearer shape:
- reusable skills instead of one-off prompts
- hooks and tests for workflow discipline
- MCP-backed access to docs, code, browser automation, and research
- cross-harness install surfaces for Claude Code, Codex, OpenCode, Cursor, and related tools
- Hermes as an optional operator shell for chat, cron, handoffs, and daily work routing
## Preview Boundaries
This is a release candidate, not the final GA claim.
What ships in this surface:
- public Hermes setup documentation
- release notes and launch collateral
- cross-harness architecture documentation
- Hermes import guidance for sanitized operator workflows
What stays local:
- secrets, OAuth tokens, and API keys
- private workspace exports
- personal datasets
- operator-specific automations that have not been sanitized
- deeper CRM, finance, and Google Workspace playbooks
## Upgrade Motion
1. Read the [Hermes setup guide](../../HERMES-SETUP.md).
2. Review the [cross-harness architecture](../../architecture/cross-harness.md).
3. Start with one workflow lane: engineering, research, content, or outreach.
4. Import only sanitized operator patterns into ECC skills.
5. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.

26
docs/releases/2.0.0-rc.1/telegram-handoff.md Normal file
View File

@@ -0,0 +1,26 @@
# Telegram Handoff For Hermes
Send this to Hermes when you want it to help package the launch workflow.
```text
Use the public ECC release pack in the repo:
- docs/releases/2.0.0-rc.1/release-notes.md
- docs/releases/2.0.0-rc.1/x-thread.md
- docs/releases/2.0.0-rc.1/linkedin-post.md
- docs/releases/2.0.0-rc.1/article-outline.md
- docs/releases/2.0.0-rc.1/launch-checklist.md
- docs/HERMES-SETUP.md
- docs/architecture/cross-harness.md
Task:
1. Finalize one strong X thread for ECC v2.0.0-rc.1.
2. Finalize one strong LinkedIn post for ECC v2.0.0-rc.1.
3. Give me one 30-60 second Hermes x ECC video script and one 15-30 second variant.
4. Tell me exactly what to record now with screen capture, face camera, and voice lines.
5. Tell me what Hermes can generate automatically after I record.
6. End with a minimal checklist of the assets or logins still needed.
Be decisive. Return final drafts plus a practical recording checklist.
```

65
docs/releases/2.0.0-rc.1/x-thread.md Normal file
View File

@@ -0,0 +1,65 @@
# X Thread Draft - ECC v2.0.0-rc.1
1/ ECC v2.0.0-rc.1 is the first release-candidate pass at the 2.0 direction.
The repo is moving from a Claude Code config pack into a cross-harness operating system for agentic work.
2/ The important split:
ECC is the reusable substrate.
Hermes is the operator shell that can run on top.
Skills, hooks, MCP configs, rules, and workflow packs live in ECC.
3/ Claude Code is still a core target.
Codex, OpenCode, Cursor, Gemini, and other harnesses are part of the same story now.
The goal is fewer one-off harness tricks and more reusable workflow surface.
4/ The rc.1 surface ships the public pieces:
- Hermes setup guide
- release notes
- launch checklist
- X and LinkedIn drafts
- cross-harness architecture doc
- Hermes import guidance
5/ It does not ship private workspace state.
No secrets.
No OAuth tokens.
No raw local exports.
No personal datasets.
The point is to publish the reusable system shape.
6/ Why Hermes matters:
Most agent systems fail in the daily operating loop.
They can code, but they do not keep research, content, handoffs, reminders, and execution in one measurable surface.
7/ ECC gives the reusable layer.
Hermes gives the operator shell.
Together they make the work feel less like scattered chat windows and more like a system you can run.
8/ This is still a release candidate.
The public docs and reusable surfaces are ready for review.
The deeper local integrations stay local until they are sanitized.
9/ Start here:
Repo:
<https://github.com/affaan-m/everything-claude-code>
Hermes x ECC setup:
<https://github.com/affaan-m/everything-claude-code/blob/main/docs/HERMES-SETUP.md>
Release notes:
<https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md>