Choose a legally distributable v1 browser workload #19
Assignees
xavierk (Xavier Karma)
Clear assignees
xavierk (Xavier Karma)
No Assignees
xavierk
xavierk
Notifications
Due Date
No due date set.
Reference: xavierk/odin#19
Reference in New Issue
Block a user
Part of Find the way to Odin’s build-ready specification.
Question
Which legally distributable, offline-capable browser responsiveness workload will Odin v1 ship and score? The selected standard profile currently names the full Speedometer 3.1 default suite, but the pinned archive lacks third-party redistribution clearance and proven offline closure. Decide whether to obtain documented grants, replace uncleared assets while preserving every official default suite, or select a different full workload with a new identity. Set a finite evidence and decision gate so an unresolved rights request cannot leave the v1 specification indefinite.
For any selected pack, require a per-file provenance/license/notice matrix, canonical content-addressed manifest, and an unscored browser smoke test with outbound network blocked. Do not call a reduced or changed suite official Speedometer 3.1. If workload identity changes, update the standard profile, browser domain membership, calibration plan, run-time budget, and validation matrix without silently carrying over previous reference values. Resolve the final choice with the human before the map's final approval.
Context: Choose Odin’s runtime and Linux compatibility contract, Verify the offline Speedometer pack and its redistribution terms, and Audit Speedometer offline pack redistribution rights.
Resolution — product owner accepted the recommended route
Odin v1 will use a new Odin-owned, offline-capable browser interaction workload for its scored browser domain. It must exercise realistic web-application interactions with a documented, reproducible protocol. The exact scenario set, implementation, native statistic, validity checks, repetitions, and artifact set are a follow-on decision in Specify Odin’s v1 browser interaction workload (link subject to ticket creation). This decision selects the route; it does not claim that a pack has been built or cleared.
The uncleared full Speedometer 3.1 archive is not a v1 distribution or score dependency. Do not distribute it, call the new workload Speedometer, transfer its native score, or reuse its calibration values. The NewsSite and other third-party rights gaps documented in Audit Speedometer offline pack redistribution rights therefore cannot indefinitely block the v1 specification. An official Speedometer option can be considered separately after rights and offline validation, outside this v1 planning route.
This supersedes only the Speedometer-specific browser portions of Choose Odin’s workload suite and run profiles, Define Odin’s median score and comparability contract, and Define Odin’s calibration procedure and release gates. The seven-domain median, full standard coverage rule, separate headed/headless cohorts, mode-specific physical reference evidence, and no-score-before-calibration rule remain. The browser domain will normalize the new workload’s own validated native statistic. The standard browser stage retains a provisional five-minute ceiling within the 10–20 minute run target; the follow-on ticket must validate or revise the protocol and budget. No shortened or partial browser run yields a valid browser domain score.
Evidence gates. Before the final build-ready specification is approved, settle the exact new workload protocol, browser-domain statistic, run-time budget, and validation cases in the follow-on ticket. Before packaging or numerical scoring, require a per-file provenance, license, and notice matrix for every shipped asset and dependency; a canonical content-addressed manifest; an unscored browser smoke test with outbound network blocked; and a new mode-specific calibration corpus under the established gates. If a required gate fails, report browser coverage as unavailable or incomplete and withhold the full headline. Do not silently substitute Speedometer or old references.
The product owner selected this route in the live wayfinder exchange on 2026-09-28. No browser pack, benchmark run, or rights clearance was produced in this planning session.