Short answer: treat the date that is tied to the same named event on a dated page from the Verification Desk as the event’s own timeline, and treat a second, differently framed date (such as a later archive capture or a separate “history” entry) as a layer about that event, not the event itself. Read the label, the page’s role, and the way the entry is anchored to decide which date belongs to the underlying event and which belongs to another source layer [1] [2] [3]. Keep each conclusion tied to the identified event and timestamp; a historical record neither proves present eligibility nor turns an incomplete attempt into evidence of rejection.
Start with the page’s role: “live desk,” “archive,” or “history”
Different pages at the GROWTH10 Verification Desk serve different purposes. That purpose helps you decide whether a date is about the event or about a source layer around it.
- Live verification desk page. If an entry appears on the main GROWTH10 Verification Desk page with a date next to the same event name, that date typically reflects when the desk recorded or confirmed that event status on that live page. It is best read as the event’s timeline as presented publicly on that page, not as a later summary [1].
- Archive page. An archive page date often marks when a particular version of a desk page was captured or stored. This date usually belongs to the archival layer: it tells you when the snapshot was taken, not when the underlying event occurred. If the archived page also shows a date inside the captured entry, keep the two dates distinct: one for the archived capture, one for the event as shown within that capture [2].
- History page. A history page aggregates prior entries or notes changes over time. Dates here tend to document when a note or change was published in the historical log. Unless the entry explicitly states it is the event date, treat it as a history-layer date about the event rather than the event itself [3].
This role-based reading prevents a common mistake: reflexively choosing the newest date. The newest date may only tell you when a page was captured or a note was logged, not when the event occurred.
Use the event’s exact name and the labeled timestamp next to it
Once you know the page’s role, look for a date that is clearly labeled next to the same event name. This pairing matters:
- If the main desk page shows “GROWTH10 [event name] — Verified on April 12, 2025,” the pairing of the event name with “Verified on” is a strong signal that April 12, 2025, is the event’s recorded verification date on that page [1].
- If the archive entry reads “Archived June 3, 2025” at the top of the page, and within that archive you can see the same event labeled “Verified on April 12, 2025,” keep them separate: April 12, 2025, remains the event’s verification date as displayed; June 3, 2025, is the archive capture date for the page containing that display [2].
- If the history page lists “Update posted September 7, 2025” for that event, read that as a historical note’s publication date unless the line clearly says it is the original event date. The event’s underlying date still comes from the entry that is labeled with the event name and its status on the relevant page [3].
If a date lacks a clear label or is disconnected from the event name, do not assume it replaces the event’s own date.
Anchor every conclusion to a directly retrieved public page
When dates conflict, prioritize what you can see on a directly retrieved public page and cite the page where the evidence appears:
- Direct page view. If you can open the live desk page and see the event entry with its labeled date, you can anchor that date to that page and treat it as the event timeline on that page [1].
- Archived page view. If you can open the archive and see the page’s capture date plus the captured entry’s internal date, you can anchor both: one to the archive capture, one to the event as shown inside the capture. Do not merge them or let one overwrite the other without a clear label instructing you to do so [2].
- History page view. If you can open the history page and see an “update posted” or similar note, treat that as a history-layer timestamp unless it explicitly states “original event date” or replicates the event’s labeled date from the main desk entry [3].
This approach preserves context: you are not choosing whichever date is newest, but assigning each date to the layer it belongs to. If you cannot retrieve the page that supposedly contains the critical label, state that the point remains unresolved until the page is visible and cite what can be seen elsewhere.
Keep the caveat front and centre: historical entries are not current status
Even when you have cleanly separated dates by layer, remember what the evidence can and cannot do:
- A desk entry date on a live page shows what the desk presented on that date; it does not prove current eligibility or continuing status beyond the page’s scope [1].
- An archive capture date proves that a certain page state existed on that capture date; it does not convert an incomplete attempt into a formal rejection, nor does it refresh the event’s status by itself [2].
- A history note shows when a change or note was posted; it is not, by itself, evidence that the underlying event occurred on that same date unless the note explicitly says so and shows the same labeled pairing with the event [3].
When in doubt, keep both dates with clear labels: “Event verified on [event-labeled date] per live desk entry” and “Page captured on [archive date] per archive snapshot.” If a third date appears in the history log, note it as “Update posted on [history date] per history page.” This keeps your record precise without overstating what any single page can establish.
A simple decision path you can reuse
- Identify the page’s role: live desk [1], archive [2], or history [3].
- Find the event’s exact name and the labeled timestamp placed with it on that page.
- Assign the date paired with the event name as the event’s date on that page.
- Assign any “archived on” or “posted on” as dates of their own layers, not the event.
- If a label is missing or ambiguous, record the uncertainty and keep both dates pending a directly viewable, labeled entry.
Applied this way, two conflicting GROWTH10 dates are not a contradiction. They are two correct dates serving different purposes: one for the underlying event as displayed, and one for the surrounding record that captured or later described it [1] [2] [3].
References
Current evidence
Read the current GROWTH10 verification record
Current cart evidence and historical records are maintained separately from this editorial guide.
Open the current record →