Read the date alongside the scope.
“Read” means the public source supported the stated field or note in that review. “Publisher date” is the date shown by the source when one was available. An older publication can still be useful reference; its age alone does not establish that a claim is wrong. A recent source read does not establish behavior inside an account.
When a field uses several sources, the register retains the earliest and latest read dates. It does not replace all of them with the newest date. An access attempt can be dated without producing supporting feature evidence. Fields without a supporting source remain unestablished.
Changes in Atlas are separate from provider releases.
A clarification can add a better reference, distinguish two mechanisms or explain a plan qualification. A recheck can leave a question unresolved. Neither is an announcement that a provider launched a feature on our review date. The history shows what our entry previously recorded and what it now records.
The register begins with documented work in this research edition. It is not an exhaustive history of every platform or a continuously monitored change feed. Open questions list the evidence needed next; they do not imply that a check has been scheduled or performed.
Use uncertainty to make a better shortlist.
If a price is unknown, avoid treating it as free. If two statements have different scopes, keep the distinction until a primary source establishes which applies. If only import is documented, do not assume export or old-chat continuity. The platform finder and comparison tool keep these gaps visible.
For actual conversation behavior, use the memory observation worksheet to record a plan, model, conditions and exact reply. A feature description alone cannot supply a measured outcome.