A company that grades trading claims for a living has to grade its own.

The reflexive test

Apply the system's own standard to the sentences the company writes.

Throughout the product, a reading is required to state what it is based on and how firm it is — a finding with a thin sample is labelled as such, a benchmark states when it was built, an unconfirmed excess is called a candidate rather than a result. Those are not decorative habits; they exist because a claim without its confidence attached will be read at full strength. Product statements are read the same way by the same people. Applying a weaker standard to them than to the machinery would be a small hypocrisy with a real cost, since the buyer has no way to tell which sentences were held to which standard.

Why the distinction gets lost

A roadmap read by a buyer flattens into a promise.

The four levels are clear to the person writing them and mostly invisible to the person reading. A prospective buyer encountering a described future edition does not naturally weight it by development stage; they weigh it by how much they want it. This is the same mechanism by which a trader reads a promising backtest as an expectation, and it is not a failure of care by either party. It means the burden sits with the statement rather than the reader — the level has to be attached to the claim, not left to be inferred.

What is deliberately not stated

No dates, because a date is the one part that cannot be honoured.

The roadmap describes directions and declines to attach delivery dates, and this is a considered position rather than evasiveness. A date is a claim about a schedule that depends on work not yet done, and software schedules are the textbook case of estimates that do not survive contact. Publishing one converts an honest intention into a commitment that will probably be missed, and a missed date damages the credibility of everything stated alongside it. Naming the sequence without the timing states what is actually known.

The specific hazard here

A future edition can be used to sell the current one, and that is where the line is.

The sharp version of the problem is commercial. A described future edition makes today's product more attractive, which creates a standing incentive to describe it confidently. That is the point at which a roadmap stops being information and becomes an inducement — and the buyer bears the whole cost if it does not arrive. The line held is that a purchase should be justified by what exists at purchase, and anything promised in addition should be identified as an addition that might not come.

• The current edition must be worth its price on its own terms.
• A future edition is a reason to be pleased later, never a reason to buy now.
• Where an upgrade is genuinely committed, the commitment is stated as a commitment.

What this permits

It is not an argument for saying nothing.

Refusing to discuss direction has its own dishonesty — a buyer choosing an instrument they intend to operate for years has a legitimate interest in whether it is being developed, and silence invites worse assumptions than a labelled statement would. The workable position is to describe the intended shape, mark the confidence level, avoid dates, and treat any statement made as something the company can be held to having said. That is more informative than both a confident roadmap and a blank page.

The key idea

The standard you sell has to be the standard you speak by.

A firm selling evidential discipline is making an implicit claim about its own conduct, and that claim is checked against the ordinary sentences it writes rather than against the machinery it ships. If product statements arrive with the certainty of a marketing document while readings arrive with confidence intervals, a reader learns something about which one the company actually believes in. Applying the same discipline in both places costs a little persuasive force and is the only version that is coherent.