ClusterView Manual is an independent technical documentation project. It exists to describe configuration behavior clearly, in one place, for readers who already work with order-flow software and need a reference that does not change its vocabulary from page to page.
This publication is not affiliated with ATAS, OrderFlow Trading, Sierra Chart, Bookmap, or any data provider. No page is sponsored, reviewed, or approved by a software vendor. References to product names are descriptive and are used only to identify the configuration surface being discussed.
What We Publish
We publish configuration notes: how a setting is structured, what it changes, and which other settings it interacts with. We do not publish market commentary, forecasts, or recommendations. We do not distribute software, host installers, or operate any kind of access service. The site is static text and images, and it is meant to be read.
Each chapter is written to stand alone. A reader who arrives from a search result should be able to use the page without reading the preceding chapters, which is why every page restates the vocabulary it depends on and links to the pages that go deeper. Repetition across pages is deliberate; a reference that assumes sequential reading is a poor reference.
Method
Configuration descriptions are assembled from documented interface behavior, repeated observation of the settings dialogs, and comparison of the same panel across sessions and instruments. When a behavior depends on the data source or the platform build, the text says so rather than presenting a single case as universal. When two plausible explanations exist, both are described and the practical test that distinguishes them is given.
Numbers in tables are ranges, not prescriptions. A row height that works on one instrument may be unusable on another, and a threshold that isolates a handful of rows in a liquid session may mark every row in a thin one. The manual consistently frames settings as starting points to be adjusted against observed behavior.
Corrections and Review
Corrections are welcome and are handled through the contact page. A useful report names the page, quotes the sentence, and describes what was observed instead. Reports that include the instrument, session template, and relevant settings are easier to verify and are usually resolved faster.
Accepted corrections are applied to the page and noted in a revision line at the bottom. We do not silently rewrite a page; a reader who cited an earlier version should be able to see what changed. Where a correction is disputed, the page states the ambiguity rather than choosing a side without evidence.
Editorial Structure
The site is organized into five sections: chart engine, depth panels, modules, data and performance, and reference. The grouping follows the object being configured rather than the difficulty of the material. A reader looking for row settings finds them under the chart engine; a reader looking for update rates finds them under data and performance. Cross-links connect the two where a setting spans both.
Pages are reviewed for three things before publication: that every claim about a setting names the panel or dialog where it lives, that no page promises an outcome, and that the independence statement is present and unmodified. The last check is not a formality. A documentation project that drifts into promotion stops being useful as documentation.
Contact and Location
The editorial office is in San Francisco. Correspondence is handled by email and through the contact form; there is no telephone support line, and the listed number is an office line for written follow-up only. We do not provide configuration support for individual workspaces, but questions that reveal a gap in the documentation are read with interest.
ClusterView Manual is published as a static reference. It has no user area, no hidden tier, and no gated archive. If a page is useful, it is useful to everyone who opens it.