Skip to content
DocumentationQualify a release
On this page

Page resources

Open Markdownllms.txtView source

Last updated

This recipe binds product qualification to one exact release instead of using a visual demo or generic scanner as evidence. Syntax and output are illustrative end-product examples.

Declare release obligations

One
qualification OrdersWebProduction@1
    accessibility wcag level: AA
    browser
        chromium
        firefox
        webkit
    assistive_technology
        nvda
        voiceover
    budget initial_document 64KiB
    budget browser_code 160KiB
    budget interaction 100ms
    security
        csp
        csrf
        trusted_markup
        disclosure

Run the selected suite

Console
one test --root OrdersWeb --profile production-qualification
Plain text
keyboard navigation passed
names, roles, relationships passed
validation and outcome-unknown announcements passed
zoom, reflow, contrast, reduced motion passed
initial document 41.2 KiB / 64 KiB
browser code 118.7 KiB / 160 KiB
interaction p95 72ms / 100ms

Automated checks contribute evidence but cannot alone claim assistive- technology or human usability conformance.

Project CI through a typed format owner

Console
one export ci github-actions --root OrdersWeb
Plain text
artifact github-actions:sha256:…
projection receipt:sha256:…
source root OrdersWeb sha256:…
loss none

The generated workflow is a disposable operational projection. It invokes the same fixed commands and does not become a second project manifest or authority path.

Benchmark and qualification evidence

Qualification evidence binds to one exact release: the release plan identifies the artifacts, targets, browsers, budgets, and checks under test, and a passing run establishes only that revision on that environment. Benchmark is the controlled home for workload, target, configuration, statistics, and comparison claims; the accessibility, budget, and CI outputs above are illustrative end-product examples rather than current qualification results.

Generated CI is a disposable projection of the same root and fixed commands, so a local run, a CI run, and a release qualification share identities without sharing authority. Read benchmark and performance evidence before treating any measured number as a product claim.

See One Web and supply chain.