The operating loop
Compound Engineering works because each stage leaves structure behind for the next run. Hermes should treat those structures as first-class context, not as chat exhaust.
Hermes-native mapping
Semantic workflow triggers, not just slash commands.
compound-engineering-workflow, grill-me, writing-plans, requesting-code-review
Cold memory, entity truth, project timelines, strategic context.
Store durable meaning about EveryInc, CE, Hermes ports, Connor-specific decisions.
Source of truth outside chat.
STRATEGY.md, docs/brainstorms/, docs/plans/, docs/solutions/, status/proof logs.
Bounded subagents for implementation, research, and reviewer lenses.
Every delegated task needs done criteria, edit boundaries, validation, and independently verified proof.
SMS/Telegram-native interface for approvals, updates, and quick routing.
Natural phrases should route to the right stage; not everything needs a slash command.
Port order
Implemented now
compound-engineering-workflow is installed as the meta-router skill. It preserves the upstream thesis and maps the CE loop onto Hermes primitives.
routerphilosophyimport rulesFirst six stage skills
compound-strategy: maintain the strategy anchor.compound-brainstorm: one-question requirements.compound-plan: traceable plans.compound-work: execution with proof gates.compound-review: multi-lens review.compound-learn: solved-problem capture.
Durable artifact system
The integration only compounds if future agents can find the outputs. Chat summaries are secondary; source-of-truth files are primary.
Strategy
STRATEGY.md captures target problem, approach, persona, metrics, tracks, non-goals.
Requirements
docs/brainstorms/ holds clarified scope, actors, flows, acceptance examples.
Plans
docs/plans/ records implementation units, tests, boundaries, stop conditions.
Learning
docs/solutions/, Hermes skills, and GBrain preserve reusable fixes and patterns.
Safety doctrine
Automation should be powerful, but side effects need gates. The workflow should prefer verified action over confident narrative.
No blind imports
Copying every upstream skill creates noise. Port the loop, then the useful lenses.
No chat-only done
Non-trivial work must leave proof files, tests, diffs, URLs, or logs.
No unverified subagents
Subagent reports are hypotheses until the parent verifies artifacts.
Recommended next move
Use the first concrete stage
Start new product or direction-shaping work with compound-strategy, then flow into compound-brainstorm, compound-plan, and compound-work.
Keep the import bespoke
Use EveryInc as the pattern library, but make the Connor/Hermes version opinionated: GBrain-first, artifact-first, gateway-native, delegated where useful, verified before done.