Methods and evidence limits

Our methods depend on the question. Package metadata can establish a published declaration. A calculation can establish a result from stated inputs. A browser run can establish what happened in a particular configuration. None of those, alone, proves every other kind of claim.

For compiled references, we publish the roster, selection rules, observation dates, source links, relevant licences, transformations and hashes. A missing field remains undeclared or unknown. A current repository flag is not backdated into an earlier release. A change in a manifest is a prompt to inspect an integration, not proof that it broke or improved.

The animation package ledger selects the highest numeric stable version published by each fixed cutoff. It compares shipped manifest declarations between populated cutoff snapshots. It does not reconstruct historical registry responses or historical latest tags. Its source check executes no package code. The asset’s own METHOD file gives the exact cutoffs, repeated-slot counting rule, lineage warnings and remaining unknowns.

For executable examples, we record the tested file, steps, browser version, operating system and observation date. A revised example is tested as revised; results from a longer fixture are not automatically transferred to a trimmed component. Negative, partial and untested outcomes stay distinct. A rerun is linked to its earlier result rather than erasing it.

Performance reports identify the measured quantity and conditions. Frame duration, long animation frames and layout or paint activity are different measurements. A display’s refresh rate and a browser’s sampling tools also limit interpretation. We make no unsupported claim that an animation is fast, smooth or universally reaches a target frame rate.

Emulation and automated inspection are labelled. They do not substitute for real touch hardware, real assistive technology or specialist review where a page makes a compliance claim. Dataset observation data is CC BY 4.0; original examples are MIT-licensed. Those licences do not relicense third-party packages, documentation, images or branding.