UHP conformance
Conformance is behavioral and revision-bounded. Current source contains 85 executable checks for UHP 2026-09-28.
Page reviewed 4 Oct 2026 Source and review policy
Current coordinates
Section titled “Current coordinates”| Coordinate | Verified state |
|---|---|
| UHP protocol | 2026-09-28 Draft |
| Conformance package | 2026.9.28.post3 |
| Executable checks | 85 |
| Core | 40 |
| Extended | 9 |
| Full | 36 |
| HarnessRouter stable release | v0.29.1 / d2572192 |
| Development main (4 Oct) | d2572192, matching stable at this check |
The package remains 2026.9.28.post3 on current upstream main. The count comes from the executable @check registry in current checks.py. HarnessRouter releases through v0.29.1 do not revise the UHP protocol or this conformance-package coordinate; v0.29.1 is a relay/publication patch, not a conformance release.
Evaluate a report against the feature you need
Section titled “Evaluate a report against the feature you need”An implementation name and a green badge are insufficient for a purchasing or integration decision. Read the report’s scope before comparing its numerator with another implementation.
| Report dimension | Question to answer | Consequence |
|---|---|---|
| Protocol and suite revision | Which dated contract and executable package produced this result? | Compare only compatible scopes; retain older denominators. |
| Requested class | Core, Extended or Full? | A Core result cannot establish higher-class file/session-management behavior. |
| Advertised capabilities | Which optional surfaces were enabled? | Skipped optional checks are not demonstrated support. |
| Passed, failed and skipped checks | What was actually executed? | A registry count is neither a pass count nor a reproduction. |
| Environment | Against which server/build/configuration? | A source report does not establish readiness of your deployed instance. |
For example, a project-authored 40/40 Core report can support that implementation’s Core claim at its stated source revision. It cannot be compared as though it were a Full 85-check run. The independent implementation directory retains those distinctions, including the difference between source evidence and this site’s own execution.
Choose the lowest class that meets your workflow, reproduce the relevant checks against an isolated authorized instance when possible, and separately assess security and deployment controls. This site does not claim to have rerun upstream reports merely by reviewing them.
Environments checks
Section titled “Environments checks”UHP 2026-09-28 adds the EN-series as capability-gated Full checks. Current source includes EN-01 through EN-09.
PR #331 moved task Environment selection to metadata.environment; EN-05 sends the override through metadata and EN-07 verifies the response echo. Package post3 adds EN-09 for the optional package-spec check endpoint.
Evidence boundaries
Section titled “Evidence boundaries”A green result must name the protocol version, package/source revision and requested class. A historical result is not upgraded when the suite grows.
Examples:
- historical 74/74 reports remain evidence for their 74-check source;
- PR #211’s 75/75 candidate result remains candidate evidence for that revision;
- later 76/76 or 84/84 results remain tied to the package/source that produced them;
- the current 85-check source does not imply an 85/85 result unless a complete run explicitly reports it;
- HarnessRouter model/support-matrix measurements are not UHP conformance measurements.
Upstream documentation drift
Section titled “Upstream documentation drift”The current Tasks chapter still contains a stale top-level environment row. The current schema, changelog, Environments chapter, PR #331, conformance checks and reference implementation use metadata.environment. Conformance evidence is therefore interpreted against the patched executable/schema behavior, with the stale table entry disclosed rather than silently copied.
Related reading
Section titled “Related reading”For the implementation path behind these checks, start with getting started and the HTTP API map. The uhp-go evidence record shows why a report must retain its source revision.