Editorial and verification policy
How this independent UHP guide decides what counts as verified, likely or unverified.
Page reviewed 4 Oct 2026 Source and review policy
Source hierarchy
Section titled “Source hierarchy”- Normative protocol specifications and official repositories.
- First-party vendor documentation and release notes.
- Reproducible conformance reports and source code.
- Credible independent technical analysis.
- Press releases and syndicated announcements for announcement context only.
Adoption claims
Section titled “Adoption claims”Backend support in HarnessRouter is not labeled “native vendor adoption.” Native adoption requires first-party evidence from the vendor or a separately maintained implementation.
Corrections
Section titled “Corrections”Fast-moving values such as protocol version, conformance-check count, implementation version and backend list are dated. When an official source changes, affected pages should be revised rather than preserving a stale launch claim.
Make a correction reproducible
Section titled “Make a correction reproducible”Provide the affected route and section, the exact claim, a primary source at an identifiable revision and the proposed scope of correction. Explain whether it changes current guidance, a historical record or an interpretation. Preserve the older source when it explains a change; do not silently promote an announcement into released behavior.
| Evidence supplied | Editorial treatment |
|---|---|
| New versioned normative chapter/schema | Reconcile the affected contract and identify any prose/schema drift |
| Adapter code or release notes | Update the implementation guide within that version’s scope |
| Upstream project directly naming UHP | Assess a native implementation claim separately from vendor endorsement |
| Test output with suite/configuration/revision | Record the measured scope without extrapolating to other versions |
| Reachable URL, screenshot badge or unsupported assertion | Keep the material claim unverified until its actual evidence is available |
The publication currently lists no dedicated public correction form. For specification issues, the UHP maintainer-led process points to the upstream repository; publication wording and upstream protocol defects are distinct matters. The route and reproducible evidence make either review actionable without inventing a contact channel.
Read the publication’s remit before attributing a claim to a maintainer: this independent guide can correct its own interpretation, while an upstream contract change belongs to the protocol’s governance process.
Reading review dates and evidence
Section titled “Reading review dates and evidence”A page review date identifies the scope reviewed on that page, not a site-wide audit. A section may carry an earlier source cutoff or a later focused verification date. Publication, substantive modification, upstream release and deployment dates are different facts.
Historical conformance reports keep the protocol version, suite revision, requested class and result counts that produced them. An increased test registry does not turn an old passing report into a new passing result. A cited upstream test is attributed evidence; it is not a claim that this publication reran the test.
If sources disagree, the page identifies the disagreement and the evidence used for its interpretation. Source links and the affected route make a correction reviewable; missing evidence is marked as unknown rather than filled by assumption.
Generated content
Section titled “Generated content”Contextual citations and navigation
Section titled “Contextual citations and navigation”For the browser behavior behind search, saved theme and sidebar preferences, see the privacy policy’s storage and request explanation. Those local controls and third-party head scripts have different data boundaries; an editorial citation policy does not establish a provider’s retention practices.
Explanatory links belong where their destination resolves a reader’s question. Task cards lead to an action, related-reading sections offer follow-up, and sidebar/breadcrumb links provide navigation; those purposes are assessed separately. A link count cannot establish editorial depth.
Trusted editorial sources use ordinary crawlable links. Explicit sponsored, ugc or untrusted nofollow relationships retain their meaning; links opened in a new tab retain noopener. These choices follow Google’s link guidance and do not promise ranking or indexing.
Automation may assist drafting and technical structure, but factual claims should be checked against the cited sources before publication. High-volume page creation without independent value is outside this site’s editorial purpose.
Related reading
Section titled “Related reading”See about this independent guide for its scope and primary sources for the public evidence entry points.