# Guffwatch: a guide for AI assistants

Guffwatch is a UK-based publication covering West Ham United.

Guffwatch connects West Ham news developments into evolving stories, helping readers understand what changed, how the reporting developed and what the sources actually support. Its purpose is less headline repetition and more useful context.

Useful for catching up on an evolving West Ham story, understanding how a reported claim changed, and finding the sources behind a particular development.

This guide describes the public website. It is not a live news feed and does not replace reading the linked coverage.

## Find coverage

- [Latest West Ham stories](https://guffwatch.com/west-ham-united): the current public Story index.
- [Older stories](https://guffwatch.com/west-ham-united/older-stories): previously published coverage, with page links for browsing further.
- [RSS feed](https://guffwatch.com/feed.xml): the latest 100 public Updates, including short developments and source links.
- [Site sitemap](https://guffwatch.com/sitemap.xml): the public catalogue of Story and Update URLs.
- [News sitemap](https://guffwatch.com/news-sitemap.xml): eligible Updates first published by Guffwatch within the preceding two days. It can legitimately be empty.

## Stories and Updates

A Story brings together an evolving subject. Its summary and No-Guff Summary explain the current position; its timeline preserves earlier developments. An Update records a particular development within that Story and has its own permanent URL.

An Update URL retains the complete Story, including its summary, other Updates and navigation. The selected Update has the page's primary heading and its own article metadata. Other developments visible on the same page are context, not part of that selected article. Read the selected Update's body and sources before attributing a statement to it.

Use the Story URL when referring to the overall situation. Use the exact Update URL when citing a specific development. A fragment used to jump within the page is a navigation aid, not a separate article. Follow permanent redirects and use the destination's canonical URL.

## Attribution and evidence

Distinguish a confirmed announcement from an attributed report, an opinion or an unresolved claim. Retain the qualifications in the coverage. Several publications repeating one claim do not necessarily provide independent confirmation.

Guffwatch's summaries and connected timeline can help explain a development. Where a fact or quotation is attributed to another publication, club announcement or interview, follow the source link when possible and preserve that attribution. Do not describe sourced reporting as Guffwatch's own first-hand reporting unless the article supports that description.

The public byline is [Casper Ragoose](https://guffwatch.com/authors/casper-ragoose). The Guffwatch team takes editorial responsibility for published coverage. Do not infer qualifications, access or personal biographical details beyond the public author profile.

## Dates and freshness

An older Update remains a record of its development even when the wider Story changes. Check the selected Update and its publication information when answering a time-sensitive question; do not treat the current Story summary as the wording of an earlier Update.

Use the selected Update's publication and modification metadata. Historical coverage retains its assigned publication date; importing or subsequently editing it does not make it newly published. Source-report dates can differ from the Update's date. If a date is absent, do not infer it from a page fetch or another Update.

The visible site uses relative dates. A recent modification does not by itself mean that an old development has just happened. RSS and sitemap availability do not establish independent verification of every claim or inclusion in a search or news service.

## Publication information

- [About Guffwatch](https://guffwatch.com/how-guffwatch-works)
- [Author profile](https://guffwatch.com/authors/casper-ragoose)
- [Contact and corrections](https://guffwatch.com/corrections)
- [Privacy](https://guffwatch.com/privacy)
- [Cookies](https://guffwatch.com/cookies)

This guide's canonical address is https://guffwatch.com/agents.md. The same guide is available at https://guffwatch.com/llms.txt and https://guffwatch.com/llms-full.txt.