About the OrderFlow Metrics ATAS Documentation Desk

01 What this desk does

OrderFlow Metrics Editorial Desk is an independent documentation unit. Its single output is a configuration reference for the ATAS (Advanced Time And Sales) platform: a written, versioned record of how order-flow displays are assembled, parameterised and read.

The desk does not distribute software. It does not host binaries, operate accounts or provide access to any trading environment. Everything published here is prose, tables and diagrams that describe settings already present in a platform the reader obtains elsewhere. The reference exists because order-flow configuration is dense: a footprint chart has dozens of interdependent options, and a note written six months ago is only useful if it states which build it described.

Work is organised around four product lines, each with a named editor and a standing review rhythm:

• Chart modules — footprint, cluster, TPO and volume profile displays.
• Replay and data — how historical tape is prepared and replayed.
• Column and tape tools — Smart DOM, Speed of Tape, filters.
• Comparative notes — neutral side-by-side descriptions across platforms.

02 How articles are sourced and dated

Every article starts as a working note. The editor reproduces a configuration from a documented test layout, records each parameter, and writes the result in ordinary sentences. Parameter names are quoted exactly as they appear in the interface so that a reader can follow the note in a live chart without guessing.

Dating is deliberate and visible. Each article carries the ordinal of the release cycle it was last verified against, and a note beneath the heading says which sections changed in that cycle. A reader can therefore tell whether a page is current or merely still on the site.

Source classes

Layout capture

A saved workspace reproduced on a fixed sample instrument, so that described values are reproducible.

Interface inspection

Direct reading of option labels and defaults in a single documented build.

Desk comparison

Side-by-side notes where two platforms expose the same concept under different names.

Reader correction

A report from the field that a value or label no longer matches, which triggers re-verification.

03 Review workflow

Two editors read every page before publication. The first checks that each described control exists and that quoted defaults are reproduced correctly. The second reads only for scope: whether the page has drifted into commentary, comparison of outcomes or anything that reads as a recommendation. Scope drift is the most common reason a draft is returned.

1. Assignment recorded in the desk register with an editor of record.
2. Draft written against a single documented build.
3. Technical read: labels, defaults, ranges.
4. Scope read: neutral description only.
5. Version stamp and change note attached.
6. Publication and listing in the reference index.

04 Scope limits and independence

The desk has no affiliation with any platform vendor. No placement is paid for, no sponsored article is accepted, and software companies are not accepted as advertisers. Where a note describes a competing product, it describes the interface as observed and states plainly that the desk has no commercial relationship with either party.

05 Corrections and how to reach the desk

Corrections are welcome and are treated as the fastest route to a better edition. A useful report names the page, the section number, the build, and what the reader observed instead. Reports that include the exact label text are resolved quickest.

The desk keeps a single register of open reports and publishes a short list of resolved corrections with each cycle. Nothing in a report is attributed without the sender's consent.

General terms of use, privacy and accessibility statements are linked from every page footer and describe how reader correspondence is handled.