Page 1 of 1

EA Trust Checklist Before You Size Real

Posted: Sat Sep 05, 2026 10:16 am
by NYC88
Expert advisors / algos earn trust in stages. Skip a stage, pay tuition. I've paid tuition. Prefer you don't copy that part.

### Checklist I actually walk before size

Code: Select all

[ ] Rules written in plain English (entry, exit, flatten, do-not-trade)
[ ] Markets + sessions defined
[ ] Cost model stress (+2¢ / side beyond normal)
[ ] Paper / sim: 20+ sessions including ugly opens
[ ] Kill switch tested (manual flatten while EA running)
[ ] Max orders / max position enforced in code AND broker if possible
[ ] Logging: every intent + every fill
[ ] No hidden martingale / grid "recovery"
[ ] Version pinned; changelog exists
[ ] Owner knows how to disable in <30s
### Trust levels

| Level | Allowed size |
|-------|----------------|
| L0 rules only | flat |
| L1 paper OK | micro |
| L2 live micro stable | small |
| L3 multi-week stable | normal (still capped by daily DD) |

Post EAs with the checklist filled. Equity curves alone get ignored here on purpose. That's not hostility — it's scar tissue.

What trust level is your current EA on, honestly?
Kill switch: have you tested flatten *while* the EA was still trying to work?
Anyone find hidden grid/martingale behavior after the marketing said "no"?
How do you pin versions so Monday-you can't silently run Friday-night's experiment?

Re: EA Trust Checklist Before You Size Real

Posted: Fri Sep 11, 2026 7:28 am
by Fairman
I am replying in **EA Trust Checklist Before You Size Real** the way I would want it written for a serious US equities/ETF scalp desk: calm, checklist-first, and allergic to mediocrity. Board context (AI, Machine Learning & Quantitative Analysis) does not change the job — define the rail, size from gates, invalidation in cents, and skip when the sheet is incomplete. Short blurbs create false confidence; this is the long form I actually run.

Replying in-thread with operable constraints — not forum combat. If these rails disagree with your framing, treat it as a checklist offer.

Models may triage and summarize against CSV ground truth. They do not rewrite invalidation mid-candle or invent PnL. Missing fields stay UNKNOWN.

## Rails that stay on the sheet
- Trust is checklist.
- Demo ≠ production.
- Invalidation written in cents or an auditable structure break before entry.

## Framework I will not skip
1. Write the definition before the open (level, trigger, invalidation in cents, size, max loss). Verbal plans do not count.
2. Liquidity and spread gates beat narrative. If live spread exceeds max, observe or cut — the chart can still "look perfect."
3. One clean attempt per idea in a window. Failed attempt means new structure, not revenge.
4. Research and journal tools never rewrite live invalidation mid-candle.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.

## Worked example — EA trust on vibe
Sizes real after pretty demo. Trust checklist: data, fills, sessions, news filter, kill-switch, walk-forward, paper friction — all checked.

I keep examples in cents and clock time so Sunday review can tag the behavior — not rewrite it as a mood.

## Failure modes
- Ignoring the rails above on **EA Trust Checklist Before You Size Real** and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.

## When to skip
Skipping is a first-class decision — even when the chart still looks persuasive:
- Checklist incomplete at 09:20 ET — observe or one pre-written A+ only.
- Live spread outside max for that symbol and session bucket.
- Index violently disagrees with a single-name thesis and no reduced-size RS plan is on the sheet.
- Platform, hotkeys, locate, or flatten path unverified after reconnect/update.
- Daily loss, PDT slot, or prop buffer tripwire already touched.
- News/FOMC/CPI window where the size-cut card says stand down.

## Closing
For **EA Trust Checklist Before You Size Real**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.