How should we distinguish planned fixes from completed fixes?
Use completed only when the source establishes completion for the product and scope you describe. The PHP2Shell collection captured on 23 October 2026 contained two wrong fixed-version answers among 148 eligible answers. Those records concern version claims; they do not measure how often planned fixes were presented as completed ones.
What we measured
Measured. The PHP2Shell method compared dated answer claims and sources with reference evidence. Of 150 planned observations on 23 October 2026, 148 were eligible and two excluded. This page uses the two wrong fixed-version answers to explain why a version statement needs verification, without supplying a present remedy.
A separate state example comes from Change Desk's software-transaction study: 150 valid answers captured on 24 October 2026 and 25 reviewed adverse cells. The 26 October method compares answers at fixed as-of cutoffs with frozen source versions. Transaction-state findings are not patch tests, and adverse cells must not be treated as the same unit as answers.
What this means for you
Reasoned. Start with the source's verb. Proposed, scheduled, released and confirmed describe different states. Copy the supported meaning with its date and scope rather than upgrading the wording to make the update sound finished. A planned availability date remains a plan until suitable evidence establishes the later state.
Then identify what completion would mean for this statement. A source may describe a released change without establishing that a particular reader has applied it. It may describe one product line without resolving another. Keep those boundaries visible instead of allowing the word fixed to cover every part of the chain.
For your own page, retain the source passage and the approval for the state you publish. If the evidence changes, update the state and effective date together. Record the earlier wording so that a correction can be understood in sequence.
Finally, separate source delivery from answer behavior. Publishing corrected wording shows what your page now says. A later answer needs its own dated observation. Neither study establishes that changing a source will make every engine adopt the new state.
- For a vendor: name the confirmed product scope and the evidence of completion.
- For a publisher: preserve planned and unresolved states when that is what the source supports.
- For an agency: check the factual state before marking a source-page deliverable complete.
Also asked as
How should we distinguish planned fixes from completed fixes?
Related
- PHP2Shell's fixed-version findings
- Change Desk's transaction-state evidence
- Date changing company facts
- Vendor-fact scope
Next step
Use the Free 10-question check (one engine). No email is needed; runs are limited per network and per day, and by the site's daily allowance. Inspect the answer's exact state claim before choosing a source correction.
To replace one unsupported completion claim with sourced wording, Fix one answer, $490.
Our answer-study method, v1.1.
Prepared by the Broadcastwell team.
Page owner: Marcus Reed, AI Specialist. Corrections: hello@broadcastwell.com