Evaluate a local pre-trade checklist before manual order entry, blocking planless, oversized, revenge-risk, market-regime-blocked, or circuit-breaker-blocked entries while journaling the decision for trader-memory-core review.

Pre Trade Discipline Gate Overview Evaluate whether a planned manual order should proceed before it is placed at the broker. This skill reads a local checklist plus optional market regime, circuit breaker, and trader memory core artifacts. It produces a pre trade discipline decision artifact and can link that artifact back to the related thesis without changing the thesis review schedule. The gate is intentionally offline. It does not place orders, cancel orders, call a broker API, or fetch market data. When to Use Immediately before placing any manual entry order When a candidate has passed chart validation and position sizing After a recent loss, to avoid revenge trades during the cooldown window When the workflow has an upstream exposure decision and circuit breaker decision When you want checklist adherence to be visible in later trader memory core reviews Prerequisites Python 3.9+ A local JSON or YAML answers file with candidate level checklist answers Optional trader memory core thesis state under state/theses/ Optional exposure decision JSON from market regime daily / exposure coach Optional circuit breaker decision JSON from drawdown circuit breaker Workflow Step 1: Prepare the Checklist Create a JSON or YAML file with candidate answers. Only actionable manual order intents are gated. Watchlist and ignore intents are journaled as NO ACTIONABLE ORDERS . Actionable intents are ENTRY READY , ACTIONABLE , ACTIONABLE DAY1 , and MANUAL ORDER . Non actionable intents such as WATCHLIST , DELAYED EP WATCH , PEAD HANDOFF , IGNORE , and REJECTED are recorded but do not create an order permission. Provide both planned risk dollars and actual risk dollars for every actionable candidate. Use a finite, non negative number or numeric string; zero is valid. Treat missing values, booleans, non numeric strings, NaN , infinities, and negative values as REVIEW REQUIRED inputs and review them before placing an order. Step 2: Run the Gate Set as of for deterministic testing or backfills: Step 3: Interpret the Decision Decision Meaning GO All actionable manual order candidates passed the checklist and upstream gates REVIEW REQUIRED Inputs are missing, unknown, or journaling failed; do not place orders until reviewed NO GO At least one actionable candidate violated a discipline rule NO ACTIONABLE ORDERS The file contains no actionable manual orders; nothing should be placed By default the CLI exits 0 for every valid decision and exits 1 only for input or runtime errors. Use fail on non go when a shell pipeline should return 2 for any non GO decision. Rules The gate blocks an actionable candidate when: The entry is not confirmed in the written plan The stop is not predefined The size is not confirmed within plan Either risk dollar field is missing or is not a finite, non negative number ( REVIEW REQUIRED ) actual risk dollars exceeds planned risk dollars trader memory core has a losing exit or partial loss inside the revenge window exposure coach recommendation is REDUCE ONLY or CASH PRIORITY drawdown circuit breaker recommendation is COOLDOWN , HALTED , or TRADING HALTED Missing or unreadable market regime or circuit breaker artifacts produce REVIEW REQUIRED for actionable orders. If no actionable order exists, the result remains NO ACTIONABLE ORDERS . Outputs The script writes: pre trade discipline decision YYYY MM DD HHMMSS.json A matching markdown report unless json only is set A JSONL journal row under state/journal/pre trade discipline/ when journal dir is provided Each candidate result includes a checklist answers object with the written plan, stop, size, risk dollar, and notes answers used for the decision, so later reviews can audit what was answered at order time. Invalid risk dollar values are stored as JSON null . Valid JSON decimals that cannot round trip through a binary float are retained as numeric strings so underflow or precision loss cannot change the gate decision. If a candidate includes thesis id and state dir is provided, the JSON report is linked into the thesis linked reports list using trader memory core link report . The skill does not call mark reviewed and does not change monitoring review dates. Resources scripts/check pre trade discipline.py Main CLI and rule engine references/discipline gate framework.md Rule definitions and integration notes skills/trader memory core/schemas/thesis.schema.json Thesis state schema Key Principles 1. Manual execution only The output is a pre broker checklist gate, not an order router. 2. Written plan first No written entry plan, stop, or size confirmation means no manual entry. 3. Producer compatible state reading Revenge risk detection follows trader memory core timestamp and outcome behavior. 4. Journal without review side effects The gate links reports to theses without advancing review schedules.

pre-trade-discipline-gate