Hermes Wiki
Synthesis/ecc-toolkit-validates-the-vaults-own-four-flavor-note-taxonomy

The ECC Harness Toolkit Research Validates a Design Choice the Vault Already Made

The connection

Three notes, read together, converge on the same principle from three different angles — layered, scoped context beats one giant instruction blob:

  • ECC Agent Harness Toolkit — a Claude Code harness toolkit whose core idea is a skills/agents/rules/hooks/instincts taxonomy: durable rules stay always-loaded, workflow-specific behavior loads only when triggered.
  • Developer/system_prompt.md — the vault's own four-flavor note structure (Fundamentals/CaseStudies/Challenges/Checklists) with pillar tagging, i.e. a vault-local instance of the exact same "keep durable rules always-loaded, load workflow-specific content only when needed" principle, designed independently of the ECC research.
  • TechResearch/system_prompt.md — the same idea applied to research retrieval: a two-mode (periodic scrape vs. deep research) trigger design that only pulls in heavier research behavior when the situation actually calls for it.

Why this wasn't visible before

Developer/system_prompt.md and TechResearch/system_prompt.md were written as scaffolding for this vault's own folder structure, not as commentary on harness design — they don't cite or reference ECC. The connection only surfaces once ECC's taxonomy paper is read as a general design pattern and held up against the vault's own architecture: both independently arrived at "scope context by trigger, don't load everything always" as the answer to the same problem (how much should an agent's instructions carry by default vs. on demand).

What this suggests

  • This is external validation, not new information — worth noting in Developer/system_prompt.md itself next time it's revisited, as evidence the four-flavor/pillar-tagging design isn't idiosyncratic.
  • ECC's specific token-optimization settings (model=sonnet, MAX_THINKING_TOKENS=10000, keep <10 MCPs/<80 tools) are concrete numbers the vault's own harness notes don't currently have — worth pulling into a Developer/Fundamentals note once that bucket gets populated (per the earlier misc-folder read, Developer/Fundamentals/ is still an empty scaffold).
  • ECC's Unified Memory Vault concept (cross-harness handoffs) and AgentShield security scanning are the two pieces of ECC without a current vault-local analog — candidates for a future Developer/Fundamentals note on harness security/portability if that becomes relevant to this vault's own Hermes tooling.
Hermes Wiki