Documentation coverage and audit scope
See the demo baseline, what the browser and platform contracts establish, and where additional acceptance is needed.
Demo baseline · November 13, 2026Product audit
The docs use the November 13, 2026 demo baseline pinned by image digest and source commit. Public routes and sign-in behavior were checked on the demo. The deployed image supplies the registered forms, field definitions, CI class policies and integration profiles. The matching source provides the gateway contract, browser routing, workflow rules and previous acceptance evidence. See the verification matrix for results from checks run against the pinned release.
The authenticated walkthrough opened 84 destinations exposed by the demo administrator's workspace finder, including entries that open the same page or a filtered view. It checked portal Home, Request something, Find answers, and My activity, opened the issue and application-access forms, and inspected the incident list and its Overview, Classification and Work tabs. The walkthrough used read-only navigation and unsaved forms. The form reference includes technical and specialized definitions as well as direct workspace forms.
Verification boundaries
Live navigation used the demo administrator. The disposable tests use synthetic users and data with the pinned platform code. Tenant-defined grants and fields, destructive operations, and provider actions require evidence for their specific configuration. The integration runbook describes the receipts that establish a real provider outcome. Gateway wildcard entries describe routing groups, and the workflow index links to procedures and their verification steps.
Documentation model
The reference uses the product collections, step-based articles, cross-links, release context, API navigation, and troubleshooting patterns reviewed in ServiceNow documentation and its API reference. The procedures and field definitions describe Qintorava Cloud.