BearBreakerProtective framework
Controls and safeguards
These overlap on purpose. Each one on its own is simple, and together they keep behaviour predictable and contained, no matter how loud the market gets.
Cooldowns in each direction
After acting one way, it waits before acting that way again. No frantic repeats.
One open order at a time
A single working order per construct. No stacking and no orders racing each other.
Size and capital limits
Size multipliers and your available capital are checked before any order is allowed to leave.
Test mode and full stop
Force-test lets you try things safely. Full pause halts everything the moment you ask.
Only one copy can run
A single-instance lock makes sure two versions can never run at once and fight each other.
An honest equity history
Failed or zero account readings are skipped, so a brief glitch never corrupts your long-term record.
Command interface
You keep your hands on the wheel
A system tray presence and a local command surface give you full operational authority. Everything stays visible, and nothing happens that you cannot see or stop.
Pause and resume
Stop and restart the whole system whenever you want.
Force test
Try a cycle deliberately, for learning or checking behaviour.
Flatten
Close everything out in one action.
Cancel orders
Clear any working orders straight away.
Live construct status
See every holding next to its TCB comparison.
Outcome journal
A plain record of what happened and why.
Performance trajectory
Your equity path over time, cleanly recorded.
Ranked watchlists
Constructs sorted by how far they have drifted.
Parameter overrides
Change thresholds and sizing without touching the core.
Notification channels
Get told what happened, where you actually look.
Every guard above is written in the source you receive, so you can read it, time it differently, or switch it off. Start with setup and requirements to see how it runs on your machine.