Verification and versions
Use this page to decide what a documentation example establishes and what still needs checking on your deployment.
Keep these versions separate
| Record | What it identifies |
|---|---|
| Documentation revision | The source commit and build of the page you are reading |
| Platform deployment | The actual server release and configuration handling your request |
| Client library | The exact library file or revision loaded by your application |
| Your application | Its source files, rules, schemas, and the saved data used by the test |
| Verification run | The date, environment, exact requests, results, and cleanup |
A documentation date or successful site build does not identify the running platform. If the deployed revision is unavailable, record unknown. Do not infer it from the docs repository or a successful request. Recheck affected behavior when the platform, client library, policy, schema, or request shape changes.
Read evidence at the right scope
- A build or link check establishes rendering and link properties, not product behavior.
- Source review explains the inspected implementation; it does not establish which revision a hosted service runs.
- A browser test with controlled responses establishes the client behavior exercised by those responses.
- A live request establishes the observed endpoint, actor, operation, representation, configuration, and result. Include refusal controls and stored readback where writes are involved.
- Text approval and formal human review are separate from execution. An unassigned reviewer or pending review stays pending.
Current complete-example check
The shared-note journey and related write/restore checks were exercised on 6 November 2026, on a disposable scope of the authorized hosted test environment. The deployed platform revision was unknown. The browser journey used Chrome; no cross-browser or offline guarantee follows from that run.
The evidence covers anonymous public writes, shape refusals, conditional saves, readback, conflicts, and a conditional authoring restore. It does not cover private-user isolation, passkey lifecycle, event-delivery recovery, external-worker side effects, or platform startup/failover. Other pages have their own evidence and limitations; this is not a certification of the entire reference.
Record a useful reproduction
Keep the public/authoring role, timestamp, known versions, actor class, document/selector, relevant policy and schema, request and response, resulting stored state, and cleanup. Redact credentials and private data. Separate an expected outcome from what actually happened, including failed attempts.
If a guide disagrees with your result, retain the result and use Troubleshooting. Avoid changing several rules at once or weakening checks until an example appears to work. Maintainers keep claim-level evidence and pending work in the repository's quality workflow; that record is more specific than a page-wide “verified” badge.