Contact Run Desk
One address, read by the desk. Corrections are the most useful thing you can send, and missing procedures are a close second.
The address
Write to [email protected]. That is the only channel the desk operates. There is no contact form on this site, no chat widget, no newsletter and no account system, which is a deliberate choice rather than an omission: a site that publishes procedure does not need to collect anything from the people reading it.
What is worth sending
- Corrections. If a procedure here is wrong, incomplete, or has been overtaken by a change in how something works, that is the most valuable message the desk receives. Include the page and the specific sentence if you can.
- Gaps. A question that arose during a live run and that no page here answers. Gaps identified by people who were actually mid-run are how the scope of this site gets decided.
- Ambiguity. A passage that could be read two ways. Ambiguous procedure is worse than absent procedure, because it is followed confidently in the wrong direction.
- Broken references. An external link that no longer resolves, or documentation that has moved.
What the desk cannot do
It cannot advise on a specific run. That includes reviewing a configuration, suggesting a threshold for your budget, diagnosing a live problem or telling you whether to stop. Those decisions require information the desk does not have and carry consequences the desk cannot share, and any answer given from the outside would be a guess dressed as guidance.
It also cannot help with a product it did not build. Questions about a tool's behaviour belong with whoever maintains that tool. Where this site describes what hosted consoles generally provide, that description is not a statement about any particular one, and the desk has no ability to influence, escalate or explain anything happening inside somebody else's software.
Finally, it will not accept guest posts, paid placements, link insertions or sponsored mentions. Messages of that kind are not answered.
Security note
Never include a private key, a seed phrase, a mnemonic or an endpoint credential in an email to this or any other address. There is no correction, question or diagnosis that requires one, and any request for one is a request you should refuse. If you have already sent a secret somewhere, treat it as compromised and rotate it rather than hoping it went unread.
How corrections are handled
Substantive corrections are made in place on the page concerned, and the page's modification date moves when they are. The desk does not silently rewrite a procedure to make an earlier version look better, and it does not delete a page because it turned out to be wrong; it fixes it. If a correction changes the meaning of advice somebody may have already acted on, the page says what changed.
Replies are not guaranteed and are usually short. A page changing is the more reliable acknowledgement.