gormes-hermes-parity

Identify and validate drift between Gormes and Hermes/Honcho via bounded parity sweeps.

9|Updated Apr 19, 2026

Search Tags:#routing #evidence #progress #parity #hermes #honcho

Ready to run

npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-hermes-parity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gormes-hermes-parity
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-hermes-parity
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-hermes-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This parity skill identifies drift and divergence between Gormes and Hermes/Honcho, enabling bounded, source-backed sweeps to align behavior and route work to the smallest applicable subskill.

Core Features & Use Cases

Bounded parity sweeps against active upstream contracts and Gormes surfaces to validate alignment.
Evidence-bound routing: collect upstream evidence and delegate, isolate tasks to specialized subskills.
Auto-selection of parity passes (survey, row-shaping, stale-upstream, implemented-feature reconciliation, handoff) for incremental improvements.

Quick Start

Invoke gormes-hermes-parity to start a bounded parity pass against Hermes/Honcho and route follow-up work to the smallest applicable subskill.

Frequently Asked Questions about gormes-hermes-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect drift between Gormes and Hermes or Honcho behavior atoms?▼

Run bounded, source-backed parity sweeps against active Hermes sources to identify drift between Gormes and Hermes/Honcho. This validates alignment across behavior atoms, upstream contracts, and progress rows, routing follow-up work to the smallest applicable subskill.

What is a bounded parity sweep for upstream contract validation?▼

A bounded parity sweep is a source-backed validation pass comparing Gormes surfaces against active Hermes sources. It uses defined pass types including survey, row-shaping, stale-upstream-check, and implemented-feature-reconciliation to collect evidence and isolate tasks.

How do I route parity discovery tasks to specialized subskills?▼

Route parity discovery tasks by collecting upstream evidence during the sweep and delegating the isolated work to the smallest applicable subskill. The sweep auto-selects pass types to generate a concise task packet for downstream implementation.

Do I need active Hermes sources to run a parity sweep?▼

Yes, running a bounded parity sweep requires access to active Hermes sources like ./hermes-agent, exact upstream refs, and canonical parity artifacts. These provide the source-backed evidence needed for validation and task routing.

What pass types are available for reconciling implemented features and checking stale upstreams?▼

Available pass types include survey, row-shaping, stale-upstream-check, implemented-feature-reconciliation, and handoff. The sweep auto-selects the appropriate pass to validate alignment and generate a downstream task packet.

What are the limitations of running parity sweeps without exact upstream refs?▼

Without exact upstream refs and canonical parity artifacts, the sweep cannot perform source-backed validation or accurately route tasks. The mechanism requires active Hermes sources and exact refs to produce a reliable downstream task packet.