01 Documentation support from the desk
The reference itself is open and free to read. Alongside it, the editorial desk runs a small documentation service for teams that need a configuration question answered in writing, an existing internal note reviewed against the current build, or a structured walk-through of a module for a group of colleagues.
These are editorial services only. The desk does not supply software, does not open access to any platform, and does not advise on what settings a reader ought to trade with. Every deliverable is prose, a table or an annotated diagram that describes the interface as observed — the same material and the same neutral voice as the published reference, produced on request and dated to a stated build.
Three levels are offered. They differ in the depth of the written answer, not in priority of access, and each can be requested through the demonstration form further down this page.
02 The three levels
Reader questions
$0A single question about a published page: a parameter name, a default value, a section that is unclear. Answered in writing within five working days by the editor of record for that product line. No scheduling and no minimum length — the reply is as long as the question requires.
Extended editorial review
$45 per articleA document of up to about two thousand words is read against the current build, section by section, and returned with inline notes, a corrected parameter table and a list of the sources used. Two rounds of written follow-up are included within thirty days.
Desk workshop
$180 per sessionA ninety-minute structured walk-through of one module for a small group, built from the published reference and a purpose-prepared worksheet. Delivered by arrangement at a time agreed in writing; a written summary is issued afterwards.
03 What each level covers
Reader questions
Typically used to confirm a single point: which section of the footprint display carries the imbalance threshold, how a column is labelled in Speed of Tape, or which build a dated page describes. The editor answers from the same register used for the reference and cites the page and section on which the answer rests.
Extended editorial review
Suited to a team that already keeps internal configuration notes and wants them checked before they circulate. The review mirrors the publication workflow: a technical read for labels and defaults, then a scope read that flags anything that has drifted into commentary. The returned document carries a change note in the same style as the published pages.
Desk workshop
A structured session for colleagues who are new to order-flow displays and need a written path through the interface rather than a demonstration. The worksheet keeps the same numbered-section format as the reference so that notes taken during the session can be filed alongside the published pages.
- Deliverable
- Always written: prose, tables, annotated diagrams.
- Voice
- The neutral engineering register used throughout the reference.
- Dating
- Every deliverable states the build it was verified against.
- Limits
- No software, no access, no statements about outcomes.
04 Response times and handling
| Level | Acknowledgement | Deliverable |
|---|---|---|
| Reader questions | 1 day | 5 days |
| Extended editorial review | 2 days | 10 days |
| Desk workshop | 2 days | By agreement |
Requests are queued in the order they are registered. Where a question duplicates an open report on the same page, the editor will fold the two together and say so in the reply rather than issuing two overlapping answers.
05 Request form
Use the form below to send a request to the editorial desk. It is a local demonstration: submitting it only opens a confirmation page in this site and transmits nothing to any server. To reach the desk in practice, write to [email protected] or telephone +1 (503) 555-0142.
Please state the page and section number you are asking about, together with the build you are reading. A question framed that way is usually answered in a single reply.