DEV · Amas · Template pending: no video transcripts yet · staging · production untouched
Amas · locked rules template · staging
Template pending: no video transcripts yet
Amas · provisional setup from posts/catalogue: ORB 1:1
Template coded in system: No
No Amas template. Generic smt-python/templates/orb_basic.yaml (09:30–09:45 range, first close beyond before 11:00, stop opposite side, 1R) is close in shape but not his rule (he targets the opposite extreme after one side forms first).
Template pending: no video transcripts yet
Source notes so far (draft, not a template, not used as an A+ gate)
Two @AmasPFT X posts (amas_orb_1to1_2026-10-01.png, amas_orb_short_mirror_2026-10-01.png) + payout post; STRATEGY_NOTES.md.
01. Instrument & data
Enable ........................... True
Instrument ...................... NQ (chart shown) [X amas_orb_1to1_2026-10-01.png]
ChartTimeframe .................. 1m chart shown; execution TF not stated [X amas_orb_1to1_2026-10-01.png]02. Sessions
Enable ........................... True
TimeZone ........................ America/New_York
ORBStart ........................ 09:30 [X amas_orb_1to1_2026-10-01.png]
ORBEnd .......................... 09:45 (first 15m candle) [X amas_orb_1to1_2026-10-01.png]03. Bias
Enable ........................... not stated
BiasMethod ...................... not stated04. Setup
Enable ........................... True
LongCondition ................... ORB low forms first → target the ORB high [X amas_orb_1to1_2026-10-01.png]
ShortCondition .................. ORB high forms first → target the ORB low [X amas_orb_short_mirror_2026-10-01.png]
AggressiveFlowFilter ............ "Aggressive buying/selling" named, undefined [X amas_orb_1to1_2026-10-01.png]05. Entry
Enable ........................... not stated
EntryTrigger .................... not stated06. Stop loss
Enable ........................... not stated
StopMode ........................ not stated (only the 1:1 RR framing)[X amas_orb_1to1_2026-10-01.png]07. Take profit
Enable ........................... True
TargetMode ...................... Opposite ORB extreme [X amas_orb_1to1_2026-10-01.png; amas_orb_short_mirror_2026-10-01.png]
RiskReward ...................... 1:1 [X amas_orb_1to1_2026-10-01.png; payout post]08. Risk & limits
Enable ........................... True
MaxTradesPerDay ................. 1 [X payout post (amas_tradeify_live_payout_2026-05-11.png)]
RiskPerTrade .................... not stated09. Filters
Enable ........................... not stated
NewsFilter ...................... not stated
Opening range = 09:30–09:45 ET first 15m candle · X amas_orb_1to1_2026-10-01.png
Note which ORB extreme formed first (low first → long, high first → short) · X amas_orb_1to1_2026-10-01.png; amas_orb_short_mirror_2026-10-01.png
Aggressive buying (long) / selling (short) seen; he does not define it · X amas_orb_1to1_2026-10-01.png
Target the opposite ORB extreme · X amas_orb_1to1_2026-10-01.png
1:1 risk-reward · X amas_orb_1to1_2026-10-01.png
One trade a day · X amas_tradeify_live_payout_2026-05-11.png
Testing rules
Tuning 1 Jan – 30 Apr · four months testOut-of-sample 1 May – 31 Jul · three months testHoldout 1 Aug – 14 Sep · about six weeks testCommission $5 round turn, NQ
01
Lock the rules before testing
Every rule is written in full as a parameter list (sessions, setup conditions, entry, stop, target, max trades, bias) with a version number and a date before any data is run. Nothing changes once testing starts. Any change is a new version, and that version starts again at rule 1.
Name the instrument and the data file. Times are New York time, prices are rounded to the tick, and contract roll weeks are removed. The same cleaned data is used in every window.
This is the only window where settings can be adjusted. Rank settings by net profit after commission. Anything with fewer than 100 trades doesn't qualify. Keep the top 20 and lock them.
Out-of-sample: 1 May to 31 Jul (three months test)
Run the locked settings once, exactly as they are. No changes after seeing the results. A setting passes if it makes a net profit and has a profit factor above 1.
A trade only counts if it passes the trader's written A-plus checklist at entry: right session, liquidity swept, bias agrees, entry model confirmed, and stop and target where the checklist says. Failures are logged as B or C trades and kept out of the results.
Every known real A-plus trade from the trader's videos or posts is traced through the A-plus definition, each filter (session, bias, sweep, timeframe, news, caps), the Roman/ZZ entry path (trigger, confirmation, order type, expiry) and the fill. Record the exact step where each one dies. Misses are fixed in the next version, never the current one.
Every result shows, in order: test number, instrument, length in words, average trade, profit factor, win rate, equity curve; then average signed ticks, trade count and drawdown.
Windows run in order, with no extra out-of-sample passes and no retuning after a peek. Under 100 trades or under about three months is a diagnostic, not a pass.