Cooldown state creates accountability inside SignalShield without claiming to block brokerage activity.
Direct answer
What are SignalShield cooldowns?
Cooldowns are discipline pauses that help traders slow down after behavior pressure rises, such as rapid trading, repeated warnings, post-loss drift, or rule pressure. They make the state visible and reviewable without directly blocking brokerage trades.
Traders whose decision quality drops after losses, rapid re-entry, repeated alerts, or other short-term behavior pressure.
Next decision
Define the exact behavior that should trigger a pause and what review must happen before the next active session.
How it works
Status first, evidence second, review always.
01
Server-side discipline logic evaluates whether behavior has crossed a cooldown threshold.
02
If cooldown starts, live system status moves from Active to Cooldown with timing and reason context.
03
Executions during cooldown remain journal-only so behavior evidence is not lost.
04
Cooldown state and reason should remain visible to the trader and admin diagnostics.
Evidence and boundaries
What must remain visible for the feature to be trustworthy.
Cooldown state should include start/until timing where applicable.
Cooldown does not erase journal history.
Cooldown expiration should be diagnosable if state becomes stale.
Related discipline tools
Use one helper at the decision point.
These public helpers prepare rules, templates, and review notes. They do not write protected settings, change live system status, or replace server-side enforcement.
No. SignalShield is not a broker and does not directly block brokerage execution. Cooldowns add accountability and friction inside the SignalShield workflow.
Can journal records still be created during cooldown?
Yes. Valid execution submissions during cooldown should remain journal-only so review evidence is preserved.
Are cooldowns shame-based?
No. Cooldowns are meant to slow the session down and make behavior review easier, not to shame the trader.
Use the smallest useful workflow
Start manually. Add connected automation only when this feature solves a real problem.
