gormes-hermes-parity

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.

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.

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.

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.

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.

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.