Skip to content

Guide — one verified task

Understand what a computed signal is

The app computes indicators ("signals") from market data in your browser. What that math is — and what it isn’t.

Where this was checked: Checked against the product source at dmitriy718/tradeflows-pro@2e5540a (2025-12-16); source audit dated 2026-09-17. That’s the source code only — we couldn’t confirm which build runs at app.tradeflows.net (deployment unverified; it answered 522, origin unreachable, at the last check on 2026-09-17).

Covers: Signals (verified in source). Steps are written at the level the audit checked — the feature exists in the pinned source. Exact labels in a running app may differ; if they do, stop and see troubleshooting.

Steps

  1. Know where the computation happens: the audited source computes indicators in Web Workers — background scripts in your own browser — from market data the app has loaded. Expected result: You can place the signal in the pipeline: data in → calculation → number or marker on screen.
  2. Read a signal as a calculation result, full stop. A signal is a rule applied to past prices (for example, an average crossing another average). It is arithmetic on history. Nothing on this site or in the audited app turns it into a recommendation to buy, sell or hold anything. Expected result: You can say "this indicator crossed because these prices averaged higher" — and nothing stronger.
  3. Try the same arithmetic yourself in the Lab: it computes a simple moving average over a fixed synthetic series, step by step, with the working shown. Expected result: You have reproduced one indicator by hand on data where the right answer is known.
  4. Keep the boundary: the audited source contains no order-execution path (verified by searching the source for broker order routes — none exist). A signal in this product cannot place a trade. Expected result: No expectation that any signal "does" anything beyond being displayed.

Not covered by this guide (verification pending)

  • The exact set of indicators the deployed app shows — verification pending: the source contains several strategy/indicator modules, but what is actually rendered in a running deployment is unverified.

Guide didn't match what you saw? Open a support request — mention this guide's name and the version label above.

In this series

Production Workflow Engineering

Need Production Automation Beyond the Browser Lab?

TradeFlows documentation and guides are free. If you want self-hosted Python 3.12 + Docker workflow operators or a custom-engineered data & alerting pipeline, start immediately with our fixed-price packages:

⚡ $19 Turnkey AI Operator Starter Kit (3 Workflows) → ⚡ $29 Workflow Friction Audit & Blueprint →