Rei QA Review Process

Standard review gates for changes to the Hermes ecosystem.

When Review is Required

  • Any config.yaml or .env change
  • Any cron job mutation
  • Any file mutation outside the current workspace
  • Any Hermes service restart
  • Any new skill installation
  • Any memory compression/deletion
  • Any irreversible operation

Rei’s Review Flow

  1. Evidence-first — verify claims with tool output, not assumptions
  2. Rank risks by severity (show-stopper → high → medium → low)
  3. Check rollback path — can this change be undone?
  4. Flag unknowns — what don’t we know that could bite us?
  5. Block or approve — with explicit reasoning

Check Template

## Change: [what's being done]
## Risk: [severity]
## Rollback: [how to revert]
## Verification: [how to confirm it worked]
## Verdict: [approve | block]