# Trader-MCP compatibility note

This note is for Hermes-MCP developers.

## Trader taxonomy expected by Hermes

Canonical strategy set currently used by Hermes supervision:
- `grid_trader`
- `trend_follower`
- `exposure_protector`

## Trader contract locations

Primary contract and runtime docs live in `trader-mcp/`:
- `trader-mcp/Hermes_Trader_Contract_v0.1.md`
- `trader-mcp/Hermes_Trader_Action_Contract_v0.1.md`
- `trader-mcp/Strategy_Contract.md`
- `trader-mcp/Strategy_Runtime.md`
- `trader-mcp/MCP_SURFACE_PROPOSAL.md`
- `trader-mcp/TODO.md`

## Hermes-facing data

Hermes should read strategy snapshots via `report()`.
Important fields:
- `identity`
- `control`
- `fit`
- `supervision`
- `position`
- `state`
- `assessment`
- `execution`

## Hermes control path

Hermes should write through one canonical Trader tool:
- `apply_control_decision(payload)`

Trader may still use these internally or for operator workflows:
- `control_strategy()`
- `set_strategy_policy()`

The current supervision facts used by Hermes include:
- `inventory_pressure`
- `capacity_available`
- `side_capacity`
- `trend_strength`
- `rebalance_needed`
- `signal`

The reports should stay descriptive, not imperative.
Hermes infers switches from the factual report plus narrative and wallet state.

Policies are still applied on reconcile and instance creation.