01 Sources
OrderFlow Metrics Editorial Desk writes about settings that can be observed in a charting workspace. A page begins with first-hand observation: the desk opens the software, changes one option at a time, and notes what each change does to the drawing on the screen. Observation is the primary source and carries the most weight.
Secondary sources are used to check vocabulary and to catch anything the desk has missed. The vendor's own help text is read for terminology, as are the published release notes for a build. Secondary sources are never used to fill a gap that observation could not close; where only a secondary source supports a claim, the page says so plainly.
02 Verification workflow
Every claim passes through the same short chain before it is published.
- Observe the setting in a clean workspace and record the steps taken.
- Repeat the observation on a second workspace to rule out a stray choice.
- Compare the wording against the vendor's help text for the same build.
- Ask a second member of the desk to reproduce the result from the written steps alone.
- Publish only what the second member can reproduce.
Rule If a step cannot be reproduced by someone who did not write it, the step is rewritten or dropped. Reproducibility, not confidence, decides what appears on a page.
03 Version notes and dating
Charting tools change. A setting that sits under one menu in one build may sit elsewhere in the next. To keep that visible, each page carries a review date at its foot and each substantive change is written into a short note.
- Review date
- The day the page was last checked end to end.
- Build reference
- The tool version the check was performed against.
- Change note
- One line naming what moved, was added or was removed.
04 Review cadence
Pages are revisited on a fixed rhythm rather than only when a reader complains. The full set is checked twice a year, in April and October. A page that names a menu path or a labelled option is checked more often, because those details drift fastest.
| Page type | Cadence | Trigger for an off-cycle check |
|---|---|---|
| Setting reference | Twice a year | A new build of the tool |
| Layout and workspace | Twice a year | A reader report |
| Policy pages | Once a year | A change in practice |
An off-cycle check is done whenever a vendor ships a build that moves a menu, and the affected pages are re-dated on the day the check finishes.
05 Conflict of interest
The desk takes no money from a platform maker, a reseller or a data provider, and it carries no advertising. No member of the desk holds a stake in a charting product, and no page is sponsored or placed. A member who develops an interest that could colour their writing steps away from the affected pages, and the change is noted in the correction log below.
06 Corrections, takedowns and the public log
A correction request is logged on the day it arrives and answered on the merits. A takedown request from a rights holder is treated as urgent: the disputed passage is set aside while it is examined, then restored with edits or removed for good. Every substantive outcome is entered in the log so the record is visible to readers.
| Date | Page | Outcome |
|---|---|---|
| 03 March 2026 | footprint-cluster-modes.html | Renamed a column label to match the current build. |
| 21 May 2026 | workspaces-and-layouts.html | Corrected the order of two docking steps. |
| 12 October 2026 | disclaimer.html | Expanded the independence statement at a vendor request. |
Requests may be sent to [email protected] or by post to 1840 Wexford Avenue, Suite 12, Portland, OR 97205, United States. This policy was last reviewed on 12 October 2026.