Free manual path
Practice the discipline loop before adding automation.
- One starter discipline system
- Manual journal and cooldown practice
- Shield Score Lite and lock preview
Product guide
Build the discipline workflow before pressure tests it.
Choose the manual or connected path, define one system, create behavior evidence, and review the state without turning SignalShield into a broker, signal service, or trade executor.
One system first
Evidence before memory
Automation only when useful
Operating overview
Start with the system state, not the next trade.
The guide follows the same path as the product: define rules, preserve evidence, and review what happened.
Direct answer
How does SignalShield work?
SignalShield creates an accountability loop around an existing trading process: define one system, receive or record evidence, apply visible cooldown or lock context, journal the decision, and review discipline quality. It reinforces rules without predicting or executing trades.
Jump to section+
01 · Choose your workflow
Start manually on Free or connect live automation on a paid plan.
The first decision is not which feature looks impressive. It is whether manual review is enough or whether live TradingView and optional Discord delivery will improve follow-through.
Paid connected path
Add TradingView when the live workflow earns its place.
- Verify the paid alert connection with a setup/test event
- Keep optional Discord delivery separate from journal proof
- Log the first real execution after connectivity is verified
02 · What happens after signup?
Start with one discipline system before adding more automation.
The first session should make the workflow understandable. Complete one control point at a time, then review the evidence before expanding the setup.
1
Start with one honest discipline system
Name the first workflow you want to protect. Free supports a manual discipline loop, so clarity comes before paid automation.
2
Define the limits before pressure arrives
Set the session rules, cooldown expectations, and lock boundaries that should remain visible when losses, alerts, or urgency build.
3
Practice manually or connect TradingView on a paid plan
Free can be used to practice manually with journaling and review. A paid alert connection can add live TradingView and optional Discord workflow delivery.
4
Send a setup test without treating it as an execution
A setup/test alert verifies the connection path. It should not become an execution record, increment behavior counters, or trigger cooldown and lock policy.
5
Log the actual execution or journal-only review
Record what happened, what was planned, emotional context, and rule adherence. During a non-active state, submissions remain journal-only.
6
Review cooldown, lock, and Shield Score evidence
Use the visible state reason, journal record, and Shield Score as behavior-review context, not as a profit score or trading-result prediction.
7
Upgrade only when automation or capacity is useful
Compare paid plans when live alerts, Discord delivery, more systems, adjustable thresholds, or deeper review support the workflow.
Protected app behavior, account access, tier limits, resets, and live guardrails remain enforced server-side after login.
03 · Build one system
Define the rules before the session can negotiate with them.
A useful system makes the intended limits visible: risk profile, trade count, loss pressure, cooldown expectations, lock boundaries, and reset policy.
System configuration
Rules stay visible before pressure rises.
Settings define the operating boundary; protected enforcement remains inside the app.
01
Limits
Define the session and risk boundaries that matter most.
02
Cooldowns
Choose when a pause should interrupt urgency.
03
Locks
Make the strongest protective state explicit.
04
Reset policy
Know what recovery requires before the state changes.
04 · Create evidence
Connect the alert to the behavior that followed it.
Alert Review preserves the pressure event. The journal preserves the decision, context, rule adherence, and emotional state. Neither should be replaced by memory alone.
Alert evidence
Review what arrived.
Validated alert context remains separate from execution and journal evidence.
Journal evidence
Record what actually happened.
The journal connects execution context, review coverage, and the session that produced it.
05 · Review behavior
Use Shield Score as review context, not a prediction.
Shield Score summarizes discipline quality and evidence coverage. A profitable session can still contain weak process, and a losing session can still show disciplined behavior.
Behavior review
Review the process behind the result.
Shield Score is not a profit score, win-rate predictor, or guarantee of future trading performance.
06 · Understand the state
Know what the state means and what should happen next.
The state is operational context. It is not a market opinion, trade recommendation, or broker-side control.
Active
The system is available for its normal discipline workflow.
Next: Follow the written rules and preserve the evidence.
Caution
Pressure is rising, but the workflow has not moved into cooldown or lock.
Next: Slow down and review the reason before another decision.
Cooldown
A temporary pause is visible after a configured trigger or voluntary lock.
Next: Respect the timer and use journal-only review.
Locked
The system is in its strongest protective state until the policy allows recovery.
Next: Do not treat the state as a signal. Review the evidence and recovery path.
07 · Free workflow tools
Add one helper where it clarifies the next decision.
These public tools prepare rules, templates, and review notes. They do not change live system status, mutate protected settings, or replace the protected app workflow.
Before setup
TradingView Alert Workflow Builder
Map alert names, expected actions, and review prompts before a webhook becomes live workflow evidence.
Map alert workflow
Webhook setup
TradingView Webhook Message Template
Draft a clean webhook message shape before connecting TradingView alerts to SignalShield visibility.
Draft webhook message
Before arming rules
Trading Cooldown Rule Calculator
Estimate a starting cooldown window from behavior pressure without writing directly to protected system settings.
Estimate cooldown
Before hard stops
Lock Rule Builder
Define the exact behavior or threshold that should move a session into review before the moment arrives.
Build lock rule
After the session
Post-Session Debrief Template
Turn completed trading into behavior evidence, review prompts, and one rule to reinforce next session.
Debrief session
After review
Shield Score Review Checklist
Review behavior quality without treating Shield Score as a profit score, win-rate predictor, or trading signal.
Review Shield Score
FAQ
SignalShield guide questions
Can I use SignalShield without TradingView automation?
Yes. Start manually on Free with one discipline system, journal evidence, cooldown practice, Shield Score Lite, and a lock preview. Paid plans add live TradingView automation and optional Discord delivery.
Does SignalShield tell me when to enter trades?
No. SignalShield is not a signal service. It adds discipline guardrails around alerts, execution logging, cooldowns, locks, and review.
What should a setup/test alert do?
It should verify the connection path without becoming an execution, changing behavior counters, or creating cooldown and lock side effects.
Important clarity
SignalShield helps traders monitor alert-driven behavior, practice cooldowns, preserve journal evidence, and review discipline patterns. It does not provide financial advice, execute trades, or guarantee outcomes.