# Hermes Concerns

This note captures the planned concern discovery and configuration flow.

## Goal
Before Hermes can run cycles, it must know what to watch.

Concerns are the input matrix. They define the account/market scopes Hermes should observe.

## Concern sources
Concerns can come from:
- Hermes configuration
- Trader strategy inventory
- manual operator entry

## Preferred order
1. Load Hermes config
2. Mirror Trader strategy inventory
3. Build the concern list from account + market coverage
4. Deduplicate concerns
5. Mark which concerns are active, paused, or informational only
6. Persist the concern registry
7. Use the registry as the stable input matrix for cycle polling

## Discovery rules
Hermes should discover:
- which accounts exist
- which markets each strategy is tied to
- whether multiple strategies share the same concern
- which concerns are missing coverage

## Configuration rules
Hermes config should define:
- watched accounts
- watched markets
- optional concern priority
- optional manual overrides
- whether Hermes may only recommend or may also act

## Important principle
Trader is the authority for live strategy instances.
Hermes may mirror and reason about them, but v1 should not auto-create instances unless a later policy explicitly allows it.

## What Hermes should remember
The concern registry should be stable enough that later cycle code can rely on it without guessing.