Daily loss caps
Set a realized-loss ceiling per session. Once hit, the scanner stops firing new candidates and marks the account cooled off until the next session boundary.
Example"Stop scanning after $500 realized loss."
Discipline layer
Markets are built to take the money you already have.
Every trader knows their own worst habits — the revenge trade after a loss, the tired lunchtime scalp, the size-up when the day is already green. Sentio's discipline layer turns those habits into hard-coded gates. Write the rule once, in plain English. If it trips, the setup is silenced and the reason is displayed. Keeping what you've made is the point.
Six rule primitives
Compose the discipline layer from primitives that mean something.
Every rule below is a real primitive you can configure per-model or session-wide. Chain them together to encode the way you already know you should trade — but sometimes don't.
Time-window mutes
Silence any model during hours you have historically traded badly — lunch chop, London-to-NY handoff, post-cash close. Muted models continue evaluating but do not push alerts.
Example"Mute Unicorn between 3pm and 6pm ET."
Consecutive-loss brakes
After N losses in a row, Sentio can halve your default size, gate you out of new setups for a cooldown window, or lock your directional bias until a winning trade resets the counter.
Example"Halve size after 2 losses in a row."
Bias locks & cooldowns
A trade closes red — Sentio can force a mandatory cooldown, or lock you to a specific direction until an intraday reset (e.g. no counter-trend entries after a loss).
Example"After a loss, wait one hour before the next trade."
Per-model rules
Every discipline rule can be scoped to a specific model or applied to your whole session. Aggressive setups can carry tighter guardrails than your bread-and-butter model.
Example"Cap Sweep Failure at 2 trades per session."
Session boundary resets
Counters, mutes, bias locks — every discipline state resets cleanly at your configured session boundary (default 6pm ET). Nothing bleeds silently into the next session.
Example"Reset all counters at the 18:00 ET session cut."
How losses stay small
The floor is arithmetic, not willpower.
Every guardrail below is a hard rule enforced in code. It doesn't nudge you, warn you, or ask if you're sure. Once the threshold trips, the affordance to take the trade is gone.
1DAILY CAP
Three losses in and the scanner goes dark.
Your realized-loss cap for the session is a number you write once. When today's aggregate hits it, the scanner stops surfacing candidates. The alert bus mutes. The decision dialog won't open. The trade you would have taken at loss #4 doesn't reach your screen.
Session P&L · today
Trades3
P&L-$500
StatusLOCKED
2COOLDOWN
After every stopout, a mandatory pause.
Set the window that matches your emotional recovery — 10 minutes, 30, an hour. Between the stopout and the timer clearing, no new alerts fire from any model. The revenge trade at 14:47 doesn't get to be a trade because there's nothing to click.
Post-loss cooldown
18:42 remaining
Alerts muted · Unicorn, Forever, IFVG
3SIZE LADDER
Size halves before your judgment does.
Consecutive losses collapse your default position size on a ladder you configure. Two losses in a row → the sizing engine cuts your contracts by half automatically. Three in a row → quarter size. The math changes the moment the second red trade closes; you don't need to remember.
Effective size · current
0 losses10 contracts
2 in a row5 contracts
3 in a row2 contracts
4 in a row0 — locked
4VETO LOG
Every vetoed setup is written down.
Rules that trip get logged with the specific value that caused the veto and the setup that would have surfaced. You can review the session and see what the day would have looked like without the guardrail — useful for tuning the cap up or down.
Vetoed today · 3
14:47 Unicorn · SHORT cooldown (18m left)
15:02 Forever · LONG daily cap hit
15:34 IFVG · SHORT daily cap hit
Tuning a model
Every threshold is exposed. Change one, see the impact.
Built-in models and custom ones you author both expose the same tuning surface: a small set of numeric thresholds, a replay validator, and a diff view. Turn one knob, re-run against 3000 historical bars, compare.
AEXPOSED KNOBS
The parameters that matter, not the ones that don't.
Every built-in model surfaces 8–20 tunable thresholds — displacement magnitude, retest window, session gates, minimum liquidity. Each one carries an inline "how Sentio interprets it" note so you can tune without guessing what the number means.
Forever · parameters
Min impulse (× ATR)1.5
Below 1.2 fires too often. Above 2.0 misses cleanest setups.
Retest window (bars)6
Wider = more triggers, weaker structure integrity.
Min confluence2
Number of independent structural conditions required.
BREPLAY DIFF
Change one parameter. See the exact impact.
The tuning loop is not "run overnight, hope for the best." Adjust a threshold, hit re-validate, watch the trigger count + expectancy shift within seconds. The diff view highlights exactly which historical trades disappeared or newly appeared.
Parameter diff
min_impulse 1.2 → 1.5
retest_bars 10 → 6
triggers · 3k bars 42 → 28
avg R +0.9 → +1.4
CACTIVATE
Ship the tuning to the live scanner.
Once the replay diff looks right, one button pushes the new parameter set to the live scanner. Old triggered_setups stay in your journal at their original parameters — no rewriting of history, no back-fitted stats.
Push to live · Forever
LIVE with new parameters
What happens when a rule trips
Gated setups are loud, not hidden.
Traders game rules they cannot see. Sentio makes the gate conspicuous — the setup still shows up, marked as blocked, with the exact rule and value that caused it. You cannot pretend the rule did not fire, and you have a clean record of what the day would have looked like without it.
- 01 Signal formed
Structural pattern completes on the timeframe. Model marks the setup as candidate.
- 02 Discipline check
Sentio evaluates every active rule against current session state — realized P&L, consecutive losses, active mutes, bias locks.
- 03 Gate or pass
If any rule is tripped, the setup is gated. The gate reason is displayed next to the model card in plain English.
- 04 Journalled
Gated setups are still recorded in the journal for post-session review — so you can see what you would have taken without the rule.
Plain English, compiled
Type the rule the way you would say it out loud.
You type
"Halve my size after two losses in a row, and stop scanning entirely if I'm down $500 realized today. Reset at 18:00 ET."
Sentio parses
- 1.
consecutive_lossesthreshold: 2 → size × 0.5 - 2.
daily_realized_lossthreshold: -500 → halt - 3.
session_resetat: 18:00 ET
Write your rules once. Let the scanner enforce them.
Discipline is included on every plan — free forever, no card.