Public documentation outline
Content source of truth: tunes. Public site hosting: likely tunes-web (landing + docs pages) linking to releases in tunes.
Site / README structure
- What is TUNES — passenger noise experience survey; open methodology + dataset; not an operator product
- Affiliation disclaimer — not TfL-operated/approved/endorsed
- How it works — ios capture → review/consent → derived upload → pipeline → open releases
- Limitations — survey-grade; consumer devices; uncertainty
- Get the app / contribute — when available
- Explore the map — with honesty explanation
- Open data — releases, licence, checksums, citation
- Methodology — protocol, metrics, tiers, calibration hierarchy
- Privacy notice — controller, retention, withdrawal (governance/legal/privacy-notice.md)
- Contributor guide — safe practice, alignment, metadata
- Researcher guide — schema, reproducibility, known biases
- Data dictionary
- Governance — ADRs, decision log, CoC, ownership statement
- Corrections & disputes — takedown/reporting
- Press / FAQ — claim-language checklist
- Contact
- Terms · Cookies · Moderation — legal pack siblings
Canonical legal drafts live in tunes; public pages ship from tunes-web via legal/consumers/tunes-web/.
Citation (draft shape)
Cite dataset release ID + schema/pipeline versions + date; cite methodology doc version separately from map screenshots.
Recommendation
Write Limitations and Privacy before marketing launch pages; keep claim language checklist on the press page.
Confidence: High for outline.
Depends on experiment/legal/user-test? Legal for privacy notice.
Links: 00-index-full.md; tunes-web/README.md; governance/licences.md.