Wyckoff AI
PSRC Wyckoff Ω2d.5 Production v1.0
Institutional Wyckoff Intelligence & Execution Framework
PSRC Wyckoff Ω2d.5 Production v1.0 is an advanced TradingView market-structure engine built to transform classical Wyckoff methodology into a causal, systematic and auditable decision framework.
Download the technical whitepaper:
Download the manual:
Rather than searching for isolated chart patterns, Ω2d.5 models the market as an evolving Wyckoff campaign—Accumulation, Distribution, Reaccumulation or Redistribution—and continuously determines where that campaign sits within Phases A through E.
The system combines structural analysis with confirmed higher-timeframe context, market-regime analytics, liquidity mapping, volatility diagnostics, VWAP positioning, relative volume and a hardened production execution layer.
Importantly, Wyckoff structure remains the sole executable signal authority. Higher-timeframe EMA alignment, Markov regime information and other contextual analytics inform the decision process but do not silently manufacture or veto trades.
1. What Ω2d.5 Is Designed to Answer
At any moment, a professional trader needs to answer several different questions:
What is the market doing?Is price accumulating, distributing, reaccumulating or redistributing?
Where are we in that process?Is the campaign still establishing a range, probing liquidity, confirming direction, or already transitioning into markup or markdown?
What evidence has already appeared?Selling Climax? Automatic Rally? Secondary Test? Spring? UTAD? SOS? SOW? LPS?
What should logically happen next?
How mature is the structure?
Does the wider market context support or conflict with the developing thesis?
Where is external liquidity?
Is volatility stable, transitional or unusually elevated?
Is an executable signal actually present—or is the chart merely displaying a developing bias?
Ω2d.5 brings those questions into a single institutional decision dashboard.
2. The Core Wyckoff Engine
Ω2d.5 models four principal structural states:
Structure | Interpretation |
Accumulation | Potential transition from selling pressure toward markup |
Distribution | Potential transition from buying pressure toward markdown |
Reaccumulation | Consolidation within a broader bullish campaign |
Redistribution | Consolidation within a broader bearish campaign |
Each campaign progresses through the traditional Wyckoff framework:
Phase A → Phase B → Phase C → Phase D → Phase E
Internally, the engine tracks the major Wyckoff events required to establish and validate the campaign, including SC/BC, AR, ST, Spring, UTAD, Tests, SOS/SOW, LPS/LPSY and eventual Markup/Markdown.
3. Understanding the Five Wyckoff Phases
Phase A — Stopping the Prior Move
Phase A represents the potential termination of the preceding directional campaign.
The engine looks for evidence such as:
PS / PSY — Preliminary Support or SupplySC / BC — Selling Climax or Buying ClimaxAR — Automatic Rally or Automatic ReactionST — Secondary Test
The objective is not to predict a reversal from one candle. The system attempts to establish that the previous directional auction may have stopped and that a trading range is beginning to form.
Phase B — Building the Cause
Phase B is the range-building phase.
Price rotates through the developing structure while supply and demand are repeatedly tested.
Ω2d.5 examines factors including:
repeated range tests;
range traversals;
opposing-edge behavior;
relative effort and spread;
structural boundaries;
range width relative to ATR;
campaign maturity.
Phase B is often where impatient traders attempt to predict direction too early.
Ω2d.5 instead treats it primarily as information acquisition.
Phase C — The Test
Phase C is one of the system's most important decision zones.
Bullish structures may produce:
Spring → Test
Bearish structures may produce:
UTAD → Test
The engine can also recognize terminal tests where a classical Spring or UTAD is absent.
Phase C attempts to answer one critical question:
Has the market successfully tested the remaining opposing liquidity before directional expansion?
For the default Standard entry profile, qualified Phase-C Tests form one of the primary executable signal classes. Wyckoff_Omega_v2d_5_Production_v1_0.pine
Phase D — Directional Confirmation
Phase D looks for evidence that control is shifting decisively.
Bullish:
SOS — Sign of Strength
Bearish:
SOW — Sign of Weakness
The system then watches for:
LPS — Last Point of Support
or:
LPSY — Last Point of Supply
These events can provide later-stage entries after structural direction has become clearer.
Phase E — Markup or Markdown
Phase E represents acceptance outside the established range.
The market has transitioned away from balance and into a directional campaign:
Markup following successful accumulation.
Markdown following successful distribution.
Phase E is therefore not simply “another breakout.” It is the culmination of the structural campaign the engine has been tracking.
4. Entry Architecture
Ω2d.5 provides three Entry Strictness modes.
Standard — Recommended Production Default
Standard is the shipping and validated baseline.
It allows quality-qualified Phase-C Tests and can fall back to LPS/LPSY when the structure develops further.
This offers a balance between:
early structural opportunity and sufficient structural confirmation.
The Production v1.0 release deliberately retains Standard rather than changing the strategy after validation.
Conservative
Conservative demands stronger campaign quality and waits for the later
LPS/LPSY class.
This produces fewer and later signals.
It should not automatically be assumed to be “better” simply because the word Conservative sounds safer. It materially changes the signal population and therefore represents a different operating profile.
Use it when your personal methodology specifically prefers later confirmation.
Aggressive
Aggressive lowers the structural qualification threshold.
It can act on qualified Phase-C Tests earlier and, where no qualifying test exists, may use SOS/SOW strength as a fallback.
It will generally produce earlier and potentially more frequent signals at the cost of requiring greater tolerance for incomplete structure.
The exact distinctions among Aggressive, Standard and Conservative are coded into the signal qualification logic rather than being cosmetic labels.
5. Entry Trigger Setting
The Buy/Sell Label Trigger lets users display particular structural reference classes:
Auto — Entry Strictness
Phase C Test
SOS / SOW
LPS / LPSY
Phase E
For normal operation, use:
Auto — Entry Strictness
This allows the production engine to use the selected Entry Strictness logic.
The other selections are particularly useful for study, chart review and comparing specific Wyckoff events.
A critical distinction:
Structural reference markers are not necessarily executable AUTO signals.
Ω2d.5 stores structural events independently, while the actual production alert originates only from the confirmed executable AUTO signal.
6. Why Ω2d.5 Uses an Institutional Architecture
The word institutional refers here to architecture and workflow—not to a claim that the indicator has privileged exchange information or secret institutional order flow.
Ω2d.5 applies several engineering principles associated with professional trading systems.
Stateful Market Modeling
The engine does not simply ask:
“Does this candle look like a Spring?”
It maintains a persistent campaign state, phase, range boundaries, structural events and progression history.
A Spring only has meaning within an established Wyckoff campaign.
That distinction dramatically separates structured market modeling from ordinary pattern recognition.
Causal Confirmed-Bar Processing
Higher-timeframe context is calculated from previously completed higher-timeframe candles rather than developing future information.
The H1, H4 and Daily EMA diagnostics explicitly use confirmed higher-timeframe values. Wyckoff_Omega_v2d_5_Production_v1_0.pine
This is an important protection against the appearance of historical perfection created by using information that was not actually available at decision time.
Separation of Intelligence and Execution
Ω2d.5 deliberately separates:
DISPLAY SOURCE
from:
EXECUTION SOURCE
The dashboard may select a more mature higher-timeframe Wyckoff campaign for situational awareness.
Production execution, however, defaults to:
Chart TF Only
This means a sophisticated higher-timeframe dashboard can inform the trader without silently taking control of the actual signal engine. Wyckoff_Omega_v2d_5_Production_v1_0.pine
This separation is one of the defining architectural features of Production v1.0.
Higher-Timeframe Context Without Hidden Vetoes
The dashboard examines:
H1 EMA20H4 EMA20H4 EMA200Daily EMA50
and reports how many are aligned with the current Wyckoff projection.
The default H4 EMA200 mode is diagnostic.
HTF alignment is not permitted to manufacture a Wyckoff signal or silently suppress one. Wyckoff_Omega_v2d_5_Production_v1_0.pine
Regime-State Intelligence
Ω2d.5 incorporates a five-state regime model:
UPTRENDDOWNTRENDRANGEHIGH VOLTRANSITION
It also estimates:
regime persistence;
transition entropy;
regime age;
exit hazard;
effective regime observations;
directional Markov alignment.
The model updates from confirmed chart data and distinguishes between WARMUP, STABLE and UNSTABLE states. Wyckoff_Omega_v2d_5_Production_v1_0.pine
Again, this layer provides context rather than hidden trade authority.
External Liquidity Context
The dashboard continuously identifies the nearest major confirmed external reference among:
PDH — Previous Day HighPDL — Previous Day LowPWH — Previous Week HighPWL — Previous Week Low
Distance is normalized in ATR units, making proximity comparable across instruments with very different price scales. Wyckoff_Omega_v2d_5_Production_v1_0.pine
VWAP and Relative Volume
The dashboard also displays:
VWAP displacement, expressed relative to ATR.
RVOL 20, comparing current volume against its 20-bar average.
On decentralized markets and many CFDs, volume should be understood primarily as tick volume rather than centralized exchange volume. Wyckoff_Omega_v2d_5_Production_v1_0.pine
Auditable Execution
Each executable signal can create a machine-readable record containing:
Signal ID
Idempotency key
Deployment ID
Symbol
Direction
Entry class
Execution timeframe
Display timeframe
Production-health status
configuration fingerprint
structural timestamps
HTF state
Markov state
This allows signal generation to be audited independently from eventual execution.
7. The Institutional Dashboard
The dashboard is designed to behave like a compact trading desk rather than a decorative indicator panel.
STRUCTURE
Shows the currently selected Wyckoff campaign:
ACCUMULATIONDISTRIBUTIONREACCUMULATIONREDISTRIBUTION
When direction has not yet been structurally confirmed, the dashboard may display a developing bias rather than a completed directional conclusion.
PHASE
Displays:
A / B / C / D / E
This is one of the most important fields on the dashboard.
The same price action means very different things depending on where it occurs within the campaign.
PROJECTION
Shows the developing structural direction and its maturity.
Examples:
ACCUMULATION BUY • 73%
or:
DISTRIBUTION SELL • 82%
This figure is not a probability of winning.
It is a structural-completion metric derived from campaign progress together with internal maturity and validation measurements. Wyckoff_Omega_v2d_5_Production_v1_0.pine
LAST EVENT
Shows the most recent major Wyckoff event recognized by the engine.
Examples include:
SC, BC, ST, Spring, UTAD, Test, SOS, SOW, LPS or LPSY.
NEXT
Identifies the event or structural behavior the engine expects to investigate next.
This makes the system useful before an entry signal appears.
A trader is not simply told what happened.
The dashboard communicates:
What would need to happen next for this thesis to mature?
DISPLAY ENTRY
Shows the entry state associated with the currently displayed structure.
Typical states include:
BIAS ONLY
PENDING
or:
FIRED — Phase C Test / LPS / etc.
Do not confuse DISPLAY ENTRY with the production execution source.
MATURITY
Measures how developed the Wyckoff campaign has become.
Higher values indicate that more of the necessary structural evidence is present.
VALIDATION
Measures how well the internal conditions supporting the identified campaign have been satisfied.
Maturity and Validation work together but represent different questions:
Maturity: How far has the campaign progressed?
Validation: How convincing is the evidence supporting that interpretation?
RANGE POSITION
Shows price location inside the current trading range:
LOW
MID
HIGH
along with an approximate percentage through the range.
This allows immediate spatial interpretation of Wyckoff events.
RANGE / WIDTH
Displays the current estimated lower and upper range boundaries and expresses range width in ATR units.
This helps distinguish a meaningful structural trading range from a trivial consolidation.
DISPLAY SOURCE
Identifies the timeframe currently powering the dashboard.
For example:
30m • MTF
while the trader may actually be viewing a 15-minute chart.
This is intentional.
The dashboard can use the more mature higher-timeframe campaign without changing the production execution source.
8. Higher-Timeframe Matrix
The dashboard includes:
Field | Purpose |
H1 EMA20 | Faster institutional trend context |
H4 EMA20 | Intermediate H4 directional context |
H4 EMA200 | Major H4 structural trend context |
D1 EMA50 | Daily directional context |
HTF ALIGN | Number of the four measurements agreeing with the current Wyckoff direction |
EXEC HTF | Current state of the selected HTF diagnostic |
A reading of:
4/4
means all four are directionally aligned.
A reading of 4/4 should be interpreted as contextual confluence, not an independent trade signal.
The Wyckoff engine remains the trade authority.
9. Markov & Regime Dashboard
REGIME
Possible states:
UPTRENDDOWNTRENDRANGEHIGH VOLTRANSITION
MARKOV
Possible interpretations include:
ALIGNED — directional regime agrees with the active Wyckoff projection.
OPPOSED — regime direction conflicts with the projection.
RANGE — current environment is range-dominant.
TRANSITION — regime is changing or does not meet strong trend/range definitions.
HIGH VOL — volatility rank has entered the high-volatility regime.
WARMUP — insufficient observations are available to characterize the transition state robustly.
These states are informational rather than automatic trade gates.
VOL RANK
Shows the percentile rank of current ATR within the model's rolling volatility sample.
A high reading indicates that current volatility is elevated relative to recent history.
PERSIST
Estimated persistence of the current regime.
Higher persistence suggests the current state has historically been more likely to remain in the same state on the next transition.
ENTROPY
Measures uncertainty across possible regime transitions.
Lower entropy suggests greater concentration in the transition probabilities.
Higher entropy suggests a less predictable state transition environment.
EXIT HAZARD
Estimates the observed hazard of leaving the current regime given its current age bucket.
This is a contextual regime-risk measure—not a stop-loss mechanism.
10. Liquidity & Execution Context
NEAREST LIQ
Shows whichever of PDH, PDL, PWH or PWL is nearest to current price.
The distance is expressed in ATR units.
Example:
PDH • 0.63A
means the Previous Day High is approximately 0.63 source ATR away.
VWAP
Shows whether price is above or below VWAP and by approximately how many ATR units.
Example:
ABOVE +0.42A
RVOL 20
Shows current volume relative to its 20-bar average.
Examples:
1.00x — approximately normal volume.
1.50x — approximately 50% above the 20-bar average.
0.70x — approximately 30% below average.
Use RVOL as evidence of effort, not as a directional signal by itself.
11. The Wyckoff Projection Bar
At the bottom of the screen Ω2d.5 displays an 11-stage meter:
DISTRIBUTION / SELL
S5 — S4 — S3 — S2 — S1 — N — B1 — B2 — B3 — B4 — B5
ACCUMULATION / BUY
N represents neutral/searching territory.
Movement toward B1–B5 represents increasing structural maturity of an accumulation/buy thesis.
Movement toward S1–S5 represents increasing structural maturity of a distribution/sell thesis.
The system increases structural progress as the campaign advances through Phases A–E and major events such as Spring/UTAD, Test, SOS/SOW, LPS/LPSY and eventual Markup/Markdown occur.
Critical Interpretation Rule
80% BUY does not mean an 80% chance that price will rise.
The percentage means:
approximately 80% structural maturity toward the active Wyckoff thesis.
The Production code explicitly treats this as structural maturity rather than win probability or a price target.
12. DISPLAY SOURCE vs EXEC SOURCE
This is one of the most important concepts in Ω2d.5.
Imagine a trader is viewing a:
15-minute chart.
The dashboard may determine that the strongest current campaign exists on:
1 Hour.
The dashboard may therefore show:
DISPLAY SOURCE: 1H • MTF
But Production v1.0 can simultaneously show:
EXEC SOURCE: 15m • CHART
That is correct behavior.
DISPLAY SOURCE
Answers:
Which Wyckoff structure gives the most useful situational intelligence?
EXEC SOURCE
Answers:
Which timeframe is actually allowed to generate the executable AUTO signal?
Production defaults to Chart TF Only specifically to prevent the informational dashboard from silently changing execution behavior.
13. Recommended Timeframes
15-Minute — Primary Production Baseline
Recommended: 15m
This is the preferred operating baseline for Production v1.0.
It provides a practical balance between:
structural resolution;
signal frequency;
noise suppression;
usable intraday execution;
higher-timeframe context;
regime diagnostics.
The production architecture has been validated principally around Chart-TF execution on the 15-minute chart.
For most users:
Start with 15m and do not change the execution timeframe simply to create more signals.
30-Minute — Slower Alternative
Appropriate for: slower intraday decision-making
30m can produce cleaner-looking structures with fewer signals.
It is particularly useful for traders who do not require the frequency of M15.
However, users should independently validate performance on their instruments rather than assume M15 expectancy transfers unchanged to 30m.
1-Hour — Structural / Control Use
Appropriate for: slower structural analysis
H1 remains fully compatible with the HTF and Markov diagnostics.
It can be useful for discretionary confirmation, swing-style analysis or slower structural monitoring.
Expect substantially fewer structural opportunities.
Do not assume that signal statistics from M15 apply directly to H1.
Below 15 Minutes
Not recommended as the default Production deployment.
Lower timeframes increase sensitivity to:
spread;
slippage;
microstructure noise;
short-lived volatility;
data-feed differences.
The engine can operate there, but Production v1.0 was not released around a sub-M15 execution mandate.
Above 1 Hour
Use primarily for broader structural analysis.
The current H1/H4/D1 diagnostic architecture and Markov implementation are designed for charts at H1 or lower; the code explicitly marks these diagnostic components unsupported above H1.
For Production execution, M15 remains the preferred baseline.
14. Recommended Production Settings
For most users, do not change the shipping defaults initially.
Setting | Recommended |
Operating Mode | Production |
Execution Source Policy | Chart TF Only |
Allow Legacy Display Source in Production | OFF |
Arm Live Entry Alerts | OFF until deployment verified |
Entry Strictness | Standard |
Buy/Sell Label Trigger | Auto — Entry Strictness |
Allow MTF Dashboard Override | ON |
Current Chart Minimum Phase | B |
Institutional Dashboard | ON |
Wyckoff Projection Bar | ON |
Show Entry Points | ON |
Structure Diagnostics | OFF unless troubleshooting |
HTF Diagnostic | H4 EMA200 |
Immediate Entry Event Logs | ON |
Production JSON Entry Alert | ON |
Evidence Pine Logs | ON |
Realtime Evidence Alerts | OFF |
These are the actual capital-preservation-oriented shipping defaults in Production v1.0.
15. Production Safety System
Ω2d.5 uses a fail-closed production architecture.
The system continuously checks several operational requirements.
Production health requires:
no forbidden source-policy conflict;
a valid Deployment ID;
the immediate entry ledger enabled;
an outcome/evidence audit path enabled.
If one of these conditions is invalid, live execution is placed into:
SAFELOCK
The effective live-arm state is then disabled even if the user requested ARM.
16. Understanding LIVE ARM
There are four operational states worth understanding.
DISARMED
Normal startup state.
Signals can still be detected and audited, but the production JSON execution alert is not transmitted.
This is the shipping default.
ARMED
Production health is valid and the user has explicitly enabled live alerts.
Executable AUTO signals may now generate production JSON alerts.
BLOCKED
The user has requested ARM but an operational condition prevents the effective arm from becoming active.
SAFELOCK
Production has detected a fail-closed safety condition.
Automation should be considered unavailable until the underlying issue is corrected.
17. SYSTEM HEALTH
Possible production health states include:
READY
Production source policy, deployment identity and audit infrastructure are valid.
SAFELOCK_POLICY
An unsafe production execution-source policy has been requested.
SAFELOCK_DEPLOYMENT
Deployment ID is missing.
SAFELOCK_ENTRY_LEDGER
Immediate entry-event logging has been disabled.
SAFELOCK_OUTCOME_LEDGER
No outcome evidence path is enabled.
Production health intentionally measures execution-system safety, not the quality of the current trade setup.
A dashboard showing:
SYSTEM HEALTH: READY
does not mean:
“This trade will win.”
It means:
“The production execution architecture is operationally healthy.”
18. Deployment ID
Before enabling automation, replace the default:
PSRC-OMEGA-PROD-01
with a unique identifier for that particular trading deployment.
Examples:
PSRC-ICM-XAU-01
PSRC-ICM-US30-01
PSRC-OANDA-EURUSD-01
Avoid using the same Deployment ID across independent execution endpoints.
The Deployment ID becomes part of the signal's idempotency identity.
19. Automated Execution & Idempotency
Ω2d.5 intentionally exposes one production automation channel:
dynamic JSON alert()
Each executable alert contains a unique:
signal_id
and:
idempotency_key
The receiving execution system must store the idempotency key before submitting an order.
If the same alert is received again:
the duplicate must be ignored.
This protects against accidental duplicate orders caused by webhook retries, network duplication or repeated downstream processing.
The source code explicitly states that automated execution should use the dynamic JSON channel and that the receiver must deduplicate by idempotency_key.
20. Do Not Automate the Structural Alerts
TradingView may expose structural alert conditions such as:
Spring;
UTAD;
Phase-C Test;
SOS;
SOW;
LPS;
LPSY;
Phase E.
These are useful analytical alerts.
They are not the production automation channel.
Automated broker/webhook execution should use only the Ω2d.5 machine-readable production JSON alert.
21. Suggested Operating Workflow
For a new deployment:
1. Load Ω2d.5 on a 15-minute chart.
2. Leave the factory Production settings unchanged.
3. Assign a unique Deployment ID.
4. Confirm EXEC SOURCE = Chart TF.
5. Confirm SYSTEM HEALTH = READY.
6. Keep LIVE ARM = DISARMED while observing initial behavior.
7. Confirm your webhook/executor can parse psrc_omega_entry_v1.
8. Confirm the receiver rejects duplicate idempotency_key values.
9. Verify symbol mapping, account selection, lot sizing and broker-specific risk controls.
10. Only then enable Arm Live Entry Alerts.
Capital preservation begins before the first trade is submitted.
22. How to Read a High-Quality Setup
A professional interpretation is not:
“The bar is green, therefore buy.”
Instead, work through the dashboard hierarchically.
First: Structure
Is the engine observing Accumulation or Distribution?
Second: Phase
Has the campaign developed sufficiently to matter?
Third: Event sequence
What has occurred?
What still needs to occur?
Fourth: Maturity and validation
Is the interpretation well developed and internally supported?
Fifth: Location
Where is price within the range?
Where is external liquidity?
Sixth: Context
What are H1/H4/D1 doing?
What regime is the market in?
Where is VWAP?
Is volume expanding or contracting?
Seventh: Execution
Has the actual Chart-TF executable signal fired?
Eighth: Safety
Is:
SYSTEM HEALTH = READY
and, for automation:
LIVE ARM = ARMED
This hierarchy prevents one attractive dashboard number from dominating the decision.
23. Example — Developing Bullish Campaign
Suppose the dashboard reports:
STRUCTURE: AccumulationPHASE: CLAST EVENT: SpringNEXT: TestPROJECTION: BUY 62%RANGE POS: LOWDISPLAY ENTRY: PendingMARKOV: RangeNEAREST LIQ: PDL 0.40AEXEC STATE: Pending
The correct interpretation is not:
Buy now.
The correct interpretation is:
The engine has identified a developing accumulation campaign with a completed Spring, but the expected Test has not yet produced an executable AUTO signal.
That distinction is fundamental to Ω2d.5.
24. Example — Mature Bearish Structure
Suppose the dashboard shows:
STRUCTURE: DistributionPHASE: DLAST EVENT: SOWNEXT: LPSYPROJECTION: SELL 84%RANGE POS: LOWHTF ALIGN: 3/4MARKOV: OpposedEXEC SOURCE: 15m ChartEXEC STATE: Pending
The trader has substantial bearish structural evidence.
But neither 84% projection nor 3/4 HTF alignment independently creates the trade.
Execution still waits for the actual configured Wyckoff entry logic.
25. Shadow Research Tags
Ω2d.5 may display:
SHADOW TEST
TF TAG
VOL TAG
These fields preserve ongoing research observations, including investigations involving 15m/30m behavior and elevated volatility.
They are intentionally labeled SHADOW.
They do not block, create or modify Production v1.0 signals.
This separation prevents unfinished research hypotheses from silently becoming live trading rules.
26. Outcome Ledger
Ω2d.5 includes an internal evidence framework for evaluating signals.
The research outcome model uses:
+1 source ATR target
versus:
−1 source ATR stop
over a:
20-bar horizon.
If neither barrier is hit, the timeout result records the directionally signed displacement in ATR units, capped between −1A and +1A.
Important
This is a signal-quality research metric.
It is not the same thing as:
real broker profit factor;
actual realized P&L;
net expectancy;
spread-adjusted performance;
commission-adjusted performance;
slippage-adjusted performance.
Do not market the Outcome Ledger as a broker backtest.
27. Capital Preservation Best Practices
The strongest use of Ω2d.5 is disciplined use.
Do not chase every developing projection.Wait for executable structure.
Do not increase leverage because multiple dashboard fields agree.Confluence does not eliminate risk.
Do not turn off the audit ledgers in Production.
Do not use Legacy Dashboard Source for normal live execution.
Do not share a Deployment ID across independent executors.
Do not allow the receiver to process the same idempotency key twice.
Do not assume performance transfers unchanged between symbols or timeframes.
Do not confuse HIGH VOL, HTF alignment or Markov state with standalone entry signals.
Do not arm automated alerts until position sizing, symbol translation, stop methodology and broker behavior have been independently tested.
28. Suggested Risk Framework
Ω2d.5 identifies structure and produces signals; position sizing and account-level risk remain the responsibility of the trader or downstream executor.
A capital-preservation-oriented implementation should independently define:
maximum risk per position;
maximum aggregate portfolio exposure;
maximum correlated exposure;
daily loss limits;
weekly drawdown limits;
maximum simultaneous trades;
spread ceilings;
slippage ceilings;
news/event policies;
emergency kill-switch logic.
No indicator can substitute for portfolio risk management.
29. Suitable Markets
Ω2d.5 is structurally suited to sufficiently liquid markets where meaningful auction behavior and trading ranges can develop, including:
major FX pairs
gold and silver
major equity indices
liquid energy markets
and other liquid instruments with reliable OHLC data.
Thin, discontinuous or highly illiquid instruments should be approached with considerably greater caution.
For CFDs and spot FX, remember that displayed volume is generally broker/tick-volume information rather than centralized consolidated exchange volume.
30. Quick-Start Configuration
For the majority of users:
Parameter | Use |
Chart | 15m |
Operating Mode | Production |
Entry Strictness | Standard |
Entry Trigger | Auto |
Execution Policy | Chart TF Only |
MTF Dashboard | ON |
H4 Diagnostic | H4 EMA200 |
Dashboard | ON |
Projection Bar | ON |
Entry Ledger | ON |
Evidence Ledger | ON |
JSON Execution | ON |
Live ARM | OFF until ready |
That is the recommended place to begin.
Change one variable at a time, and treat a materially different configuration as a different trading system rather than assuming the original validation automatically applies.
31. What Ω2d.5 Is Not
Ω2d.5 is not:
a guarantee of profitable trades;
a magical buy/sell predictor;
an order-flow feed;
a substitute for position sizing;
a substitute for stops;
a substitute for portfolio risk management;
or a promise that every correctly identified Wyckoff structure will resolve as expected.
It is a systematic framework for turning complex market structure into an organized, causal and auditable decision process.
32. The Design Philosophy
Most retail indicators attempt to answer:
Should I buy or sell?
Ω2d.5 asks a more sophisticated series of questions:
What campaign is developing?
What phase are we in?
What evidence has already appeared?
What must happen next?
How mature is the thesis?
What does the wider market environment look like?
Has an executable signal actually fired?
Is the production environment healthy enough to transmit it?
That is the distinction between a signal generator and a decision architecture.
PSRC Wyckoff Ω2d.5 Production v1.0
Structure first.
Context second.
Execution only when confirmed.
Capital preservation always.
PSRC Ω2d.5 converts classical Wyckoff market logic into a modern, multi-timeframe institutional decision and execution framework—while keeping signal authority, contextual intelligence and production automation deliberately separated.
Important Risk Disclosure
Trading leveraged financial instruments involves substantial risk and may result in losses exceeding expectations. Historical testing, signal-quality measurements and structural analysis do not guarantee future results. Ω2d.5 is an analytical and execution-support framework; users remain responsible for trade selection, account risk, order sizing, stop placement, broker configuration and compliance with applicable laws and platform requirements.
Automated execution should not be enabled until the complete signal-to-broker pathway has been independently tested in a non-production environment.
Comments