Escalate the workflow when a normal pause is not enough.
Lock context keeps the reason, state, and required review visible before the system returns to active use.
Direct answer
What are SignalShield lock rules?
Lock rules are stronger discipline controls that move a protected system into Locked state when hard thresholds or serious behavior patterns are reached. The lock should explain what happened, preserve evidence, and route the trader into review.
Traders who need a stronger stop state after severe threshold breaks, repeated drift, or a session that should not continue normally.
Next decision
Define the hard boundary, the visible reason for the lock, and the reset access available on the selected plan.
How it works
Status first, evidence second, review always.
01
Server-side logic evaluates hard thresholds such as execution limits, daily loss pressure, repeated cooldown violations, or severe rule breaks.
02
When lock starts, live system status reflects Locked and the event should include a stable reason code.
03
Manual reset availability remains tier-governed and server-enforced.
04
Journal history and event history remain available for review.
Evidence and boundaries
What must remain visible for the feature to be trustworthy.
Locked state should not delete history.
Manual resets must enforce ownership, tier, state, and audit events.
Lock messaging should explain the trigger and what to review.
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.
