Forward website
No club badges are deployed
The current Gameweek Explained home, Episodes and Premier League supporting routes use no club badge, crest, kit or league-image assets.
Rights and provenance
What we used. Where it appears. What the record proves.
This repository explains how Gameweek Explained documents third-party visual material, source history, actual public use, corrections and removals. Transparency can show what was used and how it was governed. Transparency does not itself create permission.
Legacy case study
World Cup Watch remains bounded
The retained historical product uses 48 national flag SVGs and five Associated Press editorial images under the existing documented controls.
Rights contact
Send and receive verified
rights@gameweekexplained.com was operationally verified in both directions on 31 July 2026; a sanitised verification record is published in the evidence layer.
Quick review
Start with the governing position.
The ordinary-reader layer is intentionally concise. Specialist records are published only when the current record itself exists; empty placeholders are not used to imply completed evidence.
Independence and Content Use Policy
The project-wide policy explains independence, identification, imagery, data, attribution, reversibility and the limits of internal governance.
Read the policy →Public-use registers
The Gate A register separates the zero-entry forward Gameweek Explained website from the retained World Cup product's exact 48 flag and five AP image uses. Live publication was verified on 19 August 2026.
Open the public-use register →Rights contact
The dedicated rights address has send-and-receive evidence, and the public contact route links directly to the concerns/corrections process.
Open rights contact →Provenance records
The Premier League/FPL public provenance edition preserves the 59-asset forensic findings and adds the current zero-use Gate A website state.
Open provenance records →Evidence
The public evidence layer provides package, visual-use, provenance and rights-contact verification summaries without publishing private source evidence.
Open sanitised evidence →Corrections and revisions
The concern process explains review and reversibility, while the revision history preserves material publication changes.
Open concerns and corrections →Current Gate A visual record
Use is recorded by surface, not by assumption.
The website, the legacy World Cup case study and the later editorial video are distinct publication contexts. A decision for one does not automatically authorise another.
Gameweek Explained website
Project-owned forward surface
The current forward routes use project-owned layout, typography and CSS presentation. No club badge family has been admitted to the Gate A website package.
- No club badge, crest, kit or league-image assets on the forward routes
- No Episode 1 release asset or video-use register
- No private archive or protected production material in the public package
World Cup Watch · historical product
Retained editorial case study
The legacy route remains public as a bounded historical product. Its admitted third-party visuals are limited to the 48 referenced flag SVGs and five owner-approved AP editorial images.
- Flag-icons source and licence notices remain in the exact public package
- The five AP images remain confined to their documented editorial cards
- An AP licence has not been established; the retained use remains a bounded editorial-risk decision
Gate A public foundation verified. The exact public package was deployed and independently verified on 19 August 2026, and owner acceptance was recorded the same day. Gate B remains separate.
Limits of the record
Documentation is not a licence.
The rights repository can document acquisition, attribution, hashes, public surfaces, controls and removals. It cannot by itself establish that every use is lawful, that attribution creates permission, that non-commercial status eliminates risk, or that a rights-holder has waived an objection.
Trace the source.
Record what file or asset was obtained, when, from where and with what confidence.
Record the actual surface.
Map only what is genuinely admitted to the publication package, including credits, excluded surfaces and removal paths.
Keep the system reversible.
Review concerns in good faith and preserve any correction, restriction, removal or replacement as a revision.