What APD does

APD continuously reads the active DCS structure and its count series. It follows the detected pushes, FCT pulls, pull terminals, and DMC totals, then checks whether those structural values form a recognized relationship. The analysis refreshes with the DCS pass and rebuilds immediately when Invert Trend changes the structure.

How APD reports a match

A ring-capable match can place a ring and connected Note Tag on the latest counted event. Every scenario glows only the sequence areas used by its rule: the applicable Push/FCT legs or totals, Initial DMC, and Pushpull 1. Overlapping scenarios combine those exact areas without adding unrelated totals. Every scenario uses a consistent three-line block: scenario label and name on line 1, the relationship values on line 2, and the relationship type in parentheses on line 3. When multiple scenarios hit together, each keeps its own three-line block with one blank line between adjacent blocks. Scenarios T3 and T8 are text-tag-only unless they occur with a ring-capable match. If any relationship value is also a structurally flagged D-Fib count, the tag adds the current parenthesized D-Fib match as its final line. Every relationship is anchored to the final EVEN event represented by its mathematical values.

R and T scenario labels start with their name only, such as Scenario R12. Click a label to expand its full details, then click again to return to name only. Double-click the full expanded label to remove it and its associated rings and glo lights. Other scenario labels keep their own highlights. Live tags, retained rAPD tags, and backtest tags share this behavior and preserve their confirmation colors and controls. Expanded details wrap into a high-contrast smart callout. The callout automatically searches for readable open space away from candles, counts and leaders, chart labels and tags, D-Fib callouts, notes, Measure readouts, and DCS cards, then reflows when the viewport or drawing layout changes. Drag the callout to place it manually; APD will preserve the user-selected position after that.

DCS-owned scenario callouts normally clear when DCS is turned OFF. Before switching it off, click rAPD in the DCS card to retain every currently displayed DCS scenario label as a permanent Note Tag remnant at the same anchor and position. The remnant preserves its multiline text and neutral, green, or red state, but becomes a fixed snapshot: live rings, BT controls, and DCS recalculation do not carry over. Use rFCT beside it to retain auto-FCTs as permanent manual FCTs.

Every local DCS relationship Note Tag is anchored to the final EVEN event represented by its mathematical values. The tag first uses its normal neutral background while it waits for the following ODD event. If that ODD event makes a strict new sequence high in an uptrend or low in a downtrend, the tag background turns GREEN. If the ODD event completes without the required limit push, the background turns RED. Only GREEN APD tags are actionable. A ring-capable relationship draws its ring only after the tag turns GREEN; neutral and RED tags never draw rings.

Every R-series and T-series APD callout has a small BT button in its upper-right corner. Click it to backtest every relationship listed in that callout from the tagged count back to the sequence start. An ODD tag checks only earlier ODD counts; an EVEN tag checks only earlier EVEN counts. Each prior hit receives a collision-aware Backtest R… or Backtest T… callout using the same values and relationship-type lines. Clicking BT again refreshes that callout's results rather than duplicating them. Backtests inspect prior EVEN mathematical endpoints only. Each occurrence is checked against its immediately following ODD event: a successful limit push produces a GREEN tag and an eligible ring only for ring-capable relationships. A failed push produces a RED tag with no ring. For a confirmed GREEN DCS R1–R9 or R11–R16 source, the same BT click also recounts the currently displayed events to the right from the source ring's mathematical anchor. Candidate values exclude the Pull's two terminal events, so adapter values 2, 6, and 10 land on EVEN right-side counted endpoints 4, 8, and 12. Count 13 is admitted only to confirm endpoint 12. Each EVEN endpoint is paired with its immediately following trend-side limit push. If the final unbeaten adapter value is 2, 6, or 10, BT adds a GREEN Backtest R10 tag and ring at its counted endpoint; a later endpoint plus limit push supersedes an earlier adapter match. Pan forward while keeping the source callout visible, then click BT without refreshing DCS. Every generated callout has an upper-right ×; clicking any one removes all generated APD backtest callouts while preserving the original APD tags. Backtest callouts are regular Note Tag drawings, so Undo, Clear Chart, and Remove Drawings (by List) can also clear them.

Local DCS APD Note Tags and rings are chart-only. Live cloud monitors analyze your saved Entry signals, including ByP, while your API selections authorize automatic trades. Telegram sends only broker-confirmed automatic trades from selected signals. Detection-only tags, rings, counts and cycles do not send messages. The shared monitor remains active; pause, resume, switch to Shadow or delete it in DCS Monitors. An enabled Live or Shadow monitor marks its stored starting candle with Monitoring in cloud · Manage; paused monitors hide that marker.

The newest eligible live DCS ring also pulses and glows the final thrust using the Reset tag candle effect. Every ring begins at its EVEN mathematical anchor and extends through new candles until the confirming ODD event appears, then remains bounded to that completed thrust. Historical rings stay visible, but only the newest eligible ring drives this pulse.

What D-Fib does

D-Fib runs four independent timing families rooted at 10, 16, 26, and 42. A family arms when the trend-START count reaches its root, then measures countable progress through the DCS sequence to find even-count endpoints where descendant routes align.

Families and routes

Each root creates its descendant line from the root, its -2 value, and the even halves that remain valid. Examples include 10/8/4/2, 16/14/8/4/2, 26/24/12/6, and 42/40/20/10.

• Two repeating routes enter the descendant line from opposite directions and cycle back through the family root.
• Four one-step main-to-main routes let a family travel directly through D10, D16, D26, or D42.
• Direct main-to-main routes are preferred in a callout when they explain the same endpoint and give that callout its light glow.

How FCT terminals are handled

Normally every FCT after a family root contributes a complete terminal pair, so both terminals are skipped at their actual counts and shown as a subtraction such as 10+8 - 2T. If a root sits strictly inside both an FCT and an Event Quad that identifies that FCT, the opening terminal is already behind the root and the crossed exit remains countable. A root directly on an FCT final terminal simply starts there; that terminal is neither counted nor deducted.

Alignments, labels, and interaction

• The side card reports confirmed alignments where two or more distinct families land together, plus each family's nearest endpoint and the next projected alignment.
• Chart-callout sensitivity can be set from 1+ through 4+ families and defaults to 1+; completed D-Fib hits must land on an even START-count value.
• A white check means the endpoint count equals DMC Total or Push 1, plus one main D-Fib value: 10, 16, 26, or 42.
• Hovering a progression illuminates its counted path; term endpoints glow more strongly and skipped terminals appear as amber crosses. Callouts can be dragged and retain their position through pan and zoom.

What ESP does

ESP is a guided endpoint-projection calculator attached to the active DCS run. Its cursor-wheel wizard collects the value-set and quota assumptions, combines them with the detected FCT/Pull structure, and displays the result as CURRENT EP in a side card. ESP operates independently from the Primes card and does not use Prime values to test or confirm its projection.

Setup inputs

• Value set: choose Single or Dual, then choose even values from 2 to 10. A dual pair is entered separately and its sum drives the downstream math.
• Push Quota mode: Halved uses Set ÷ 2; Repeated uses Set × x1 through x4; +2 sums 2 to 5 progression terms beginning at Set, such as 6+8+10 = 24.
• Uncounted events: add 0, 2, 4, 6, or 8 events that are not yet part of the displayed DCS structure.

CURRENT EP calculation

ESP begins with RGB = Set × 3, adds the selected Push Quota, adds two pull-terminal units for every qualifying DCS FCT/Pull, then adds the selected uncounted events. In compact form:

CURRENT EP = RGB + Push Quota + Pull terminals + Uncounted events

An underwater FCT is discounted as weaker structure: each one removes 1 from the FCT/Pulls count and therefore removes 2 from the pull-terminal contribution. The side card exposes the underwater count whenever this adjustment is active.

Live behavior

• The side card shows every input and contribution, with EP-contributing rows highlighted and CURRENT EP displayed prominently.
• The projection follows DCS updates automatically, including rebuilt pull structure and underwater-FCT changes.
• During setup, scroll to choose, click to confirm, and use right-click or Escape to cancel. The completed configuration persists with the active DCS state.