What problem does it solve? It prevents false confidence in bench testing by enforcing that journey changes in the gentle-ai bench corpus are proven through driven harness execution, not just go test ./bench, which only validates corpus declarations. ## Core Features & Use Cases - Journey Authoring Rules: Enforces unique journey IDs across journeys_*.go files, mandatory Review: declarations, and runnable commands on every execute transition. - CI Reproduction Guidance: Directs you to copy the exact build and gentle-ai-bench run --binary ... commands from the Unit Tests step in .github/workflows/ci.yml, using --only <journey-id> for single journeys. - Semantic Change Auditing: Requires grepping the corpus for journeys pinning old behavior when a ratified product semantic changes, so stale assertions do not keep defects green. - Use Case: When adding a new journey or diagnosing a bench failure in CI, follow the contract to produce PR evidence containing the driven-mode summary line (completed / unsupported / failed counts) from a locally built binary. ## Quick Start Ask the assistant to add a new bench journey to the gentle-ai corpus and verify it with the driven harness using the exact CI invocation.