Verify the offline Speedometer pack and its redistribution terms #16
Assignees
xavierk (Xavier Karma)
Clear assignees
xavierk (Xavier Karma)
No Assignees
xavierk
xavierk
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: xavierk/odin#16
Reference in New Issue
Block a user
Part of Find the way to Odin’s build-ready specification.
Question
Can Odin prepare and redistribute the complete Speedometer 3.1 asset pack from release commit
1386415be8fef2f6b6bbdbe1828872471c5d802afor offline loopback hosting in the selected standard browser workload? Identify the exact source and third-party assets needed, their individual license and notice obligations, any resource URLs or runtime fetches requiring closure, and whether prepared native headed/headless automation changes the pack boundary. Provide a content-addressed manifest plan and a non-benchmark offline validation procedure. If any component prevents redistribution or offline operation, state the concrete blocker and the replacement or acquisition decision it forces.This is research for the workload packaging decision. Do not run the benchmark, install browsers, or modify the host.
Research resolution
The pinned Speedometer 3.1 commit is a plausible source for a versioned, loopback-hosted static pack. Its archive contains 1,118 files (61,022,359 uncompressed bytes), 32 declared suites, and 20 default-enabled suites. All declared suite entry paths exist. Static inspection of 194 asset references from the landing page and default suite entries found no missing or external target. The Perf Dashboard workload's 13 mocked JSON paths are present.
This is a conditional packaging answer. Static checks do not prove all dynamic requests stay local. Require a blocked-network browser smoke test, without starting a scored benchmark, before calling a prepared pack offline-ready. Serve the frozen files over loopback HTTP, log attempted outside requests and console errors, and reject an incomplete pack. Use a canonical manifest with every shipped path, byte length, SHA-256, upstream commit, suite list, and notice inventory; hash the manifest for the pack identity.
The root BSD-style license permits redistribution when its notice, conditions, and disclaimer are retained as specified. TodoMVC carries MIT terms, and generated bundles include third-party notices. Preserve all notices and inline notices. A complete per-asset license audit remains open; this research cannot yet authorize redistribution of every final asset. A follow-up ticket will resolve that boundary.
Prepared native headed or headless automation does not change the static workload pack. Browser binary, driver, profile, window state, and headed/headless mode belong to run environment identity. Upstream instructions favor a focused headed page; headless results need a distinct comparison cohort. The runner's 800×600 suite iframe differs from the page's warning below an 850×650 visible viewport; record both.
Read the primary-source research report. Evidence is committed on
research/speedometer-offlineat408611d59fdac713676c533a2be82c09918e021c.No benchmark ran, no browser was installed, and the host was not modified.
xavierk referenced this issue2026-09-27 19:09:49 +00:00
Correction: this research ticket is not resolved. The static pack inventory and preliminary license findings are useful evidence, but the question asks for individual redistribution obligations across the final asset set. That audit remains open in Audit Speedometer offline pack redistribution rights. Reopening this ticket and making that audit a blocker. Once the audit is complete, resolve the exact pack boundary, required notices, and any replacement or permission decision here. The prior comment is interim research, not a final resolution.
Research resolution
The unchanged pinned Speedometer 3.1 pack is not cleared for redistribution or verified offline use. The 1,118-file source archive is inventoried, but that inventory does not establish a final runtime set or per-file rights. The NewsSite template has no visible redistribution grant. Chart datasets, Adobe Spectrum-derived assets, Project Gutenberg conditions, and component-to-notice mapping for generated bundles and imagery remain unresolved. Nine existing notice files must be retained where applicable, but notices cannot replace a missing grant.
The selected full default workload therefore requires verifiable grants and complete notices, or cleared replacements followed by rebuild and validation. If that cannot preserve every default suite, Odin must choose another browser workload or explicitly define a derivative suite and scoring identity; it cannot silently label a reduced suite as official Speedometer 3.1.
A final pack needs a per-file provenance/license/notice matrix and canonical content-addressed manifest. Before packaging, a separate unscored, outbound-blocked browser smoke test must prove every enabled suite's local resource closure, including dynamic imports, fonts, images, workers, and Perf Dashboard fixtures. Prepared browser automation and headed/headless mode belong to run environment identity, not the frozen asset pack. No browser was installed or benchmark run; neither rights clearance nor offline validation is claimed complete.
Read the source-grounded report. Evidence:
research/speedometer-pack-decisionat26dbe21c37970bc63050a5246aa5600a5243b585. Choose Odin’s runtime and Linux compatibility contract owns the resulting packaging/workload choice.