Plan the trade.
Manage the position.
Understand the result.

Augmented Trader is Sentinel’s responsive web cockpit. Its chart-led Trade, Manage, Setups and Preflight views bring the core workflow into a remote workspace: inspect the market, prepare a setup, review the checks and use the controls supported by the connected system. It gives Sentinel another surface to work from, while execution remains dependent on the backend, trading terminal and the capabilities exposed by the relevant adapter.

Know which account and market you are working with before a draft becomes an action. Account-bound settings and plans help keep context attached to the intended destination, while readiness information surfaces issues such as stale quotes or unavailable trading permissions. This matters when you change charts, reconnect or work across accounts: the workspace should make the current context visible before you rely on it.

Work with entry, stop loss and take profit levels where the decision happens: on the chart. Supported builds let you place, move, inspect, lock and retract planning levels, keeping the visual setup aligned with its numerical values. Independent locks help preserve a level you have already chosen while adjusting another part of the trade. These are planning controls; placing a line is a separate step from submitting an order.

Keep more than one idea ready without treating every draft as a live instruction. Setup slots preserve prepared intent, while preparing and arming separate an idea on the chart from a submission-ready setup. The MT5 development workflow binds saved setups to their account and symbol and gives armed intent an expiry. The visible prepared and armed states help keep preparation separate from commitment.

Make a management approach repeatable without rebuilding it for every trade. Profiles and Plan Studio organise named, revisioned plans for trailing, breakeven, partial exits and review. Choose the policy, inspect its settings and identify the positions it should apply to. Keeping the policy revision visible helps distinguish the plan you meant to use from later edits, and provides a clearer handoff into position management.

See the reasons behind an entry decision before adding exposure. Trade Clearance evaluates the available plan and account evidence and can return an allowed, caution, reduced-size or blocked outcome. It keeps the relevant reasons, plan revision and expiry alongside that decision, so a changed setup does not quietly reuse an old answer. A missing required input can block entry; clearance is a rule check, never a prediction that a trade will succeed.

An order request and a confirmed broker outcome are different events. Sentinel’s execution workflow tracks pending, partial, rejected and uncertain results, with recovery and duplicate-prevention controls designed to prevent a casual retry from becoming a second trade. Reconciliation checks what the broker actually reports before the workflow moves on. This makes uncertainty visible when connections or responses are interrupted, instead of presenting an unconfirmed request as completed.

Choose how the stop should respond as a trade develops. The MT5 development set includes independent breakeven rules and fixed, step, original-risk, closed-bar ATR and candle-structure trailing approaches. These give different ways to express the management idea, from a measured distance to a rule based on market structure. Select the method and parameters appropriate to the plan, then inspect how that policy is applied to the position.

A preserved MT5 reference uses a Standard stop-ratchet policy capped at entry, with its own partial-exit rules. Similarly named MT4 and MT5 modes must be checked against their specific build rather than assumed to behave identically.

Plan how much of a position to close at each stage and how much to leave running. Partial exits at chosen steps use the original position volume as their reference in the MT5 development workflow, with a reserve for the runner. This makes the intended distribution of exits easier to understand as the position changes. You can review the balance between taking profit along the way and keeping a defined portion exposed to the rest of the move.

Act on a single position or a clearly defined group. Supported controls can work at ticket, symbol, strategy or account scope, with a preview of the affected positions and volume before applicable close, delete or other actions. Confirm the intended scope and check the reported result. Account-mode restrictions and uncertain outcomes remain relevant, especially when several positions are involved or an action is routed through a remote connection.

Some native reference/development variants include reverse and hedge actions. Account mode and the actually exposed controls determine their availability; the current chart captures do not demonstrate those operations. MT4-specific reference tools include manual-trade takeover, selected-trade level adjustment and pending-order workflows. They are separate from the compact MT5 control set.

Use the paired Trade Manager to select trades, inspect their state and request a policy change without losing the link to the underlying trading engine. The interface identifies the target, requests the selected policy and presents the acknowledgement and available review data. That visible request-and-result relationship helps you distinguish an intended change from one the EA has actually accepted, keeping management decisions traceable to the position.

Keep declared challenge rules beside the trading decisions they affect. Prop Guard and Challenge Mode track configured targets, limits and remaining room, helping you review whether another entry fits the selected programme rules. The reset time and calculation basis matter as much as the headline limit, so the account must be configured against the actual provider’s terms. Monitoring can support discipline; it cannot guarantee a challenge pass or provider compliance.

Give a personal account the same attention you give a challenge account. Use the supported risk and analytics views to inspect exposure, drawdown context, margin pressure and recorded performance, then compare that picture with your own trading limits and goals. The value is a clearer view of what is already at stake before you add another position.

Keep operational changes within view while you trade. Sentinel’s alert and awareness work brings together acknowledgements, delivery failures, quote freshness and connection or recovery incidents, helping explain when a control or data point needs attention. Delivery options depend on the terminal and build. A terminal alert, email or push route has its own setup and limitations; the developing Android app has a separate local-notification mechanism.

Reference alert families include configured money, margin, session, news, custom-condition and trade events. Event support and delivery routes are build-specific; a local acknowledgement does not establish external delivery.

Understand more of the story around a release. The Advanced News Interpreter is designed to explain actual results against expectations, revisions, potential scenarios and usable historical context, helping you ask better questions about the event behind a price move. The interpreter is being developed as a separate MT5 tool; bringing that intelligence into Sentinel remains planned. Its analysis would add context to review, rather than a guaranteed market direction or an automatically executable signal.

Read a setup in its surrounding market context. Session views and higher-timeframe lenses help relate the current chart to a parent candle or a relevant trading window, making it easier to inspect where a move sits within a broader structure. Choose the context appropriate to the question you are researching and keep it alongside the chart. That wider view helps you examine the same setup through both its immediate movement and its surrounding session or candle.

Map the idea before deciding what to do with it. Lines, rays, zones, channels, triangles and Scenario Path give different ways to express levels and possible price paths on the chart. You can inspect and adjust the visual reasoning rather than leaving it in a separate note. Integration is being developed in phases. An illustrative scenario remains separate from an armed trading setup, leaving you in control of when research becomes a trading decision.

Give chart work enough structure to remain useful after the first drawing. Smart objects add identity, role and revision to a chart object, while Inspector and Object Manager support inspection, grouping, visibility and lifecycle actions such as archiving. This helps organise a busy chart and retain the meaning of a level as it changes. Sentinel’s Object Manager integration is currently deferred. In the separate Chart Interaction component, that persistent identity provides a foundation for connecting chart context to later review.

The proposed object-to-plan reference can carry a level’s identity and revision toward planning. Its recorded contract is local preparation only; a working Panel transport, consumer and confirmed handoff are not established.

Follow what happens to an important level after you mark it. Object alerts can describe events such as a touch, break, close beyond a level or time condition, with rearming and persistent event records in the component design. The useful connection is between the specific object, its condition and the event that occurred.

Add profile context to a Fibonacci-based chart study. Fib Volume Profile provides source-labelled levels that help you inspect where the underlying data places activity within the selected research view. Read those levels alongside the source and calculation basis rather than assuming every profile describes the same market information. Tick or estimated volume must be interpreted as that data type; it is not a substitute for verified exchange order-flow data.

Keep gap research organised as the chart develops. The Smart FVG work covers discovery and promotion into managed gap objects, bringing a candidate area into the same object-based inspection and lifecycle approach. That helps you revisit which gap was identified and how it is represented, rather than relying on an anonymous box. You can keep the identified area connected to the object you inspect as the chart changes.

Explore how a setup unfolds one bar at a time. The native MT4 analysis tools include bar-stepped review, spread-adjusted levels, partial markers and Fibonacci analysis, giving you a structured way to inspect a scenario before comparing it with real trading records. Control the progression and examine the levels as the chart advances. Replay is a research aid, and its representation of a setup should remain distinct from live broker execution.

Express a chart condition in a form you can inspect and reuse. The MT4 condition creator supports named conditions assembled from operand sources, comparisons, joins and timeframe choices. It helps make an idea explicit: what is being compared, on which timeframe, and how the parts relate. The current creator work is focused on MT4. Its place in the wider workflow is to make the rules behind an idea explicit before you decide how they should be tested or used.

The native MT4 alert/condition family includes joined AND/OR conditions, timeframe choices and reusable presets. A condition or notification is separate from an explicitly armed action; no matching MT5 builder is implied.

Find candlestick observations worth a closer look. Pattern Radar supports scheduled checks, chart navigation and recorded alerts, helping you find and revisit the observations that match the configured scan. It belongs to the research stage of the Sentinel ecosystem, where a finding can be investigated before a plan is formed. Pattern Radar studies chart patterns; account exposure is the separate role of Risk Radar.

Add focused research views to the chart with Sentinel’s indicator work. Each indicator has its own purpose, settings and platform scope, so the useful starting point is the specific study you want to inspect and the build that supports it. These tools complement the broader planning and review workflow by providing additional chart context. Platform scope and integration are specific to each indicator project.

Turn a strategy idea into visual rules you can examine on closed bars. Strategy Lab combines rule building, profiles and chart visualisation, helping you see how the configured logic is represented before you consider further testing or implementation. It is a visual research tool at its current stage. Its visual output gives you material to inspect and develop further; live order execution is outside its current scope.

Branching paths mean alternative next steps according to your conditions. In first-trigger behaviour, the first matching route can be selected and the other routes in that same step cancelled. Other steps remain independent. The current chart shows a simple sequence, rather than a complete map of every branch.

The prototype saves your design locally as JavaScript Object Notation (JSON), a text-based format for saving structured data. It stores the steps, conditions, possible responses, routes, next-step targets, labels, chart placement and selected step or route. Temporary dry-run state and logs are not saved with the design.

A dry run previews the configured sequence and proposed actions locally without sending live trade commands. It is not a historical backtest or proof of profitability. This is a separate design prototype; it has no live execution connection to Sentinel or a broker.

Move a configured idea into editable source for further development. Generator Lab generates and exports MQL4 code, giving you something concrete to inspect, compile and qualify against the intended behaviour. The generated output still needs testing and review; an export is not certification that a strategy is correct or suitable for live use. MT5 generation remains planned.

Review a manually configured plan in a TradingView-oriented workflow. TradingView Playbook gives that chart plan a defined place in the wider Sentinel research story, helping you keep the setup and its intended interpretation in view. Its current scope is the manually configured plan itself. Broker execution and account synchronisation are outside this tool’s established scope.

Review results at the level of a complete trade, including the exits and costs that can otherwise be scattered across records. The analytics work groups partial exits into trade episodes and provides filters and qualified measures based on the evidence available. Recorded net results help make costs visible, while risk-based metrics need reliable original-risk data. Where that foundation is missing, the review should show the limitation instead of inventing a precise comparison.

Broader MT5 development includes symbol, session, direction and risk-band breakdowns, net costs, counts and other qualified statistics alongside sample size. Realised R (results expressed relative to the trade’s recorded original planned cash risk) and excursion measures need reliable original risk and price-path evidence.

Separate the economics recorded on the account from estimates about how execution affected them. Execution Quality is designed to make that distinction visible, so you can inspect booked results and estimated execution drag without treating both as equally certain. Incomplete evidence remains part of the picture. This gives the review a clearer basis for asking where costs arose and how much of the explanation is supported by the record.

Preserve the information needed to understand a problem. Recovery Centre checks settings and evidence stores, keeps damaged records available for investigation and prepares redacted diagnostics for supported troubleshooting. It belongs beside review because a broken or incomplete record affects what you can conclude from the history. Its recovery work concerns settings and evidence, keeping troubleshooting separate from broker actions.

Build familiarity with the workflow through structured lessons and practice. Academy work includes learning progression, resuming an activity and offline-learning support, so a concept can be revisited as you work through the product. It connects product concepts with the planning, management and review activities you are learning to use. Web development has its own scope, and shared progression across native surfaces is not yet established.

Carry enough context forward for a result to remain meaningful later. Progress and evidence-handoff work is intended to preserve original risk, costs, consent and record lineage as trading evidence moves toward review surfaces. That continuity would help explain what a result represents and where it came from. The connected review workflow is still in development, including the production synchronisation needed to move records between surfaces.

Present a recorded result with its calculation basis visible. Result-card work includes return on margin calculated from net profit divided by the recorded entry margin, expressed as a percentage. This gives a specific view of an outcome when that margin evidence exists. Where entry margin is missing, the result is unavailable. Historical margin capture in actual-account feeds remains unfinished.

The member PWA work explores an installable evidence and learning surface, while Follow Terminal presents read-only terminal information with freshness states. Together, they offer a future place to inspect supported records and learning material without implying control of the trading terminal. This is separate from the native Android app and remains outside the current launch. Read the freshness labels alongside terminal information so you know what the view can support.

Product education explains how to configure and use Sentinel’s tools, understand platform and development labels, and inspect the responses to the trader’s chosen instructions. Technical support helps describe setup or software problems without requesting broker credentials or telling customers which trades to take. Member learning and connected support services remain in development; use the public contact page for product questions.

cTrader is a planned extension of Sentinel’s platform family. The aim is to bring the product’s connected workflow to another trading environment while respecting that platform’s own capabilities and integration requirements. Scope and availability will depend on the implementation and its qualification.

Use native controls to prepare or request the actions supported by the connected backend and terminal. Development work covers entry and sizing parameters, targets and management requests such as breakeven, trailing, partials and closes, with other actions dependent on the system’s capabilities. The important moment is the returned acknowledgement or updated snapshot. A tap on the phone starts a request; confirmation must come back from the connected trading system.

Local notifications are being developed to draw your attention to supported changes while you are using the app. They give the mobile view another way to surface something worth checking, alongside the relevant account or position information. Background delivery is still unverified, so alerts while the app is closed are not promised.

The phone handles the native interface, session and local notification presentation. The backend supplies state and routes commands. The desktop or VPS trading terminal and EA perform supported execution and automation, then return acknowledgements and snapshots. This division makes the app a companion within Sentinel’s workflow, with the connected system doing the trading work. The current Android bridge is MT4-specific. The behaviour of automation after closing the app is still being verified and should not be assumed.