How should we date an AI-facing incident statement?
An incident statement needs dates that identify what happened, which source version supports the claim and when the answer was observed. PHP2Shell's study retained 148 eligible answers captured on 23 October 2026. That capture date dates the observation; it cannot silently become the incident date or proof that the answer remains current.
What we measured
Measured. PHP2Shell's method record fixes the answer collection to 23 October 2026: 150 planned observations, 148 eligible answers and two exclusions. Its review compares captured answers and cited sources with dated reference evidence. The date and base let a reader locate this collection. They do not supply a current technical assessment, and a later source should not be substituted into the historical observation without explanation.
What this means for you
Reasoned. Label the dates by the event they describe. A single Updated line may tell a reader that a page changed without explaining when the underlying assessment became effective.
| Date field | What the reader needs to know |
|---|---|
| Incident or change date | When the reported event or state took effect, if established. |
| Source revision | Which advisory or official statement supports the claim. |
| Answer capture | When this particular AI answer was observed. |
| Fact review | When someone checked the statement against its evidence. |
Use a full timestamp and timezone where the order of events affects the conclusion. If only a calendar date is known, retain that precision instead of inventing a time. If the event date is unknown, name that gap and keep the source's known publication or revision date separately.
When revising the page, distinguish a formatting update from a changed factual assessment. Preserve the previous source and the reason for the new statement in your records. A reader should be able to understand whether the fact changed, the evidence improved or only the presentation was corrected.
An archived answer can remain useful evidence of what was said on its capture date. Its age alone does not show whether the underlying fact is now correct; that requires a current source check.
- For a vendor: place the effective fact date beside the claim it governs.
- For an agency: preserve capture and review dates as separate fields.
- For a reader: ask which date actually supports the present conclusion.
Also asked as
How should we date an AI-facing incident statement?
Related
- PHP2Shell's dated collection
- How time changes evidence
- Correct outdated company facts
- Preserve the original answer
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. Save the check's observation date with the result.
To correct one page's factual date or state with its supporting source, 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