The right first message names a figure, not a feeling — every number on this site carries a declared source, so a dispute can start precisely. And it attaches nothing: this tool exists so your documents never travel, and that starts here.
Write to contact@cascade-routing.com — the direct channel. For anything worth deciding in the open — a disputed figure, a wrong line, a question others will have — open an issue at github.com/ArslaneSempai-ui/cascade-routing. An issue is public, so put nothing confidential in it: no client names, no records, no internal figures. Either way, attach nothing: a channel for records is opened in the engagement letter, before signature, like every other term.
The page you are on and the figure you dispute — each one here has a declared source, so we can meet at it. If you disagree with a measurement, better than an argument: the record is sealed and the command is public, so bring your own rerun. If you measured your own cases, bring the report the tool wrote beside your CSV — it contains rates and intervals, never the values from your documents.
Your records. Not even a sample. The tool exists so your documents never leave your machine; a sample attached to a public issue is published, and no apology deletes a clone. If your question needs your data, the answer is a command that runs where the data lives, and we will point you to it.
Two shortcuts. On a fresh clone, node src/premiere-reponse.mjs prints the conclusion in under a second, with what would flip it. And the eight objections a bank's reviewers actually raise are already answered, mechanism by mechanism, in Appendix C — Questions below.