diff --git a/docs/binance-strategy31-volume-reversal-development.md b/docs/binance-strategy31-volume-reversal-development.md
index 1edbea2..5121783 100644
--- a/docs/binance-strategy31-volume-reversal-development.md
+++ b/docs/binance-strategy31-volume-reversal-development.md
@@ -6,10 +6,16 @@ Install alongside CorsairQuant signal client 0.6.7, which owns private gateway
 authentication. The shared bridge explicitly advertises the `strategy31` capability.
 
 CorsairQuant confirms consecutive closed red/green candles when green base volume
-strictly exceeds red base volume. This client reads native chart candle times
+has percentage growth strictly above the configured server-side
+`signal_conditions.minimum_volume_growth_percent` (20% as shipped), with positive
+red volume. Exactly 20% does not qualify at that threshold. The monitor publishes
+the startup policy in SQLite; the gateway uses that policy for retained events.
+Configuration changes require monitor restart and do not backfill previously
+discarded candles. Telegram period exclusions are separate: qualified 5m arrows
+remain available while 5m notifications are muted. This client reads native chart candle times
 only to limit rendering to loaded history; it does not detect signals locally.
 It requests a bounded snapshot of up to 200 retained
-events for the current canonical symbol and native timeframe every five seconds.
+qualifying events for the current canonical symbol and native timeframe every five seconds.
 Hidden documents suspend requests; navigation and settings revisions invalidate
 late responses. Repeated snapshots reconcile one arrow per stable event ID.
 Interval changes preserve the native data-completion subscription. Unsupported
@@ -29,7 +35,11 @@ The projection is recent retained history, not all visible chart history.
 
 The shared capability permits only `/v1/strategy31/events` with exactly `symbol`,
 `timeframe` and `limit=200`. It does not expose credentials or an arbitrary URL
-proxy. Server contract uses schema 1 and `31_2_spec_v1`. Invalid event identity,
+proxy. Server contract uses schema 1 and `31_2_spec_v1` as stable wire identity;
+runtime signal policy uses v9. The server filters before selecting the latest 200
+matches and returns them chronologically. If the 10,000-candidate scan budget is
+exceeded before filling the snapshot, the route returns 503 rather than silently
+returning incomplete history. Invalid event identity,
 coordinates or numeric values stop this observer with a visible status.
 
 Build with `npm run build:binance-strategy31-volume-reversal`; validate with