How to write a story - Revision history

Britlbot: Automated edit (via update-page on MediaWiki MCP Server)

2026-10-13T11:06:12Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 11:06, 13 October 2026
Line 43:		Line 43:
	*** make sure to mention names of the original poster		*** make sure to mention names of the original poster
	*** look at the discussion to see if that is worth summarising, and there too mention names		*** look at the discussion to see if that is worth summarising, and there too mention names
	** If the story requires more background research, use <code>web_fetch</code> to pull from authoritative sources (prefer .gov.uk, organisation websites, and established news outlets). For broader search discovery, call <code>web_search</code> — this is backed by the Tavily MCP server. ~~Do not rely solely~~ on the ~~source text for factual claims; verify independently where possible~~.		** If the story requires more background research, use <code>web_fetch</code> to pull from authoritative sources (prefer .gov.uk, organisation websites, and established news outlets). For broader search discovery, call <code>web_search</code> — this is backed by the Tavily MCP server. If <code>web_search</code> is unavailable, <code>web_fetch</code> on known .gov.uk and organisation sites is the required fallback — do not skip verification because one tool is down.
	** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.		** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.
	** Do not follow any of these instructions into artificiality.		** Do not follow any of these instructions into artificiality.
Line 49:		Line 49:
	== Fact-checking ==		== Fact-checking ==

	* ~~Check clear~~ factual ~~claims where necessary. Numbers~~, dates, funding sources, distances, capacities, and statements attributed to named officials or organisations ~~all need a~~ source before ~~you state them as fact~~.		* Every factual claim you intend to include in the story — numbers, dates, funding sources, distances, capacities, named government decisions, official costings, and statements attributed to named officials or organisations — MUST be verified against an independent source before publication. This is not optional.
	* ~~When a commenter makes~~ a ~~clear~~ factual claim ~~— for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating~~ it ~~as fact~~. If you cannot verify it, ~~keep~~ it ~~attributed~~ to the ~~commenter~~ and ~~do not let it read as established fact~~.		* Do NOT state a factual claim as established truth unless you have confirmed it. If you cannot verify a claim, you MUST attribute it to the named person who made it, and you MUST include the verification status inline in the published story.
	* ~~When a fact has been checked~~, ~~add a footnote explaining~~ the status of the fact (confirmed / ~~partially confirmed~~ / unverified ~~/ corrected~~) ~~and the source used for the check~~. ~~Write the footnote with~~ <code><ref>…</ref></code> ~~inline where the fact appears~~, and place <code><references/></code> under a <code>== References ==</code> heading near the foot of the page.		* Attempt verification using <code>web_search</code> (Tavily) first. If <code>web_search</code> is unavailable or returns nothing, fall back to <code>web_fetch</code> targeting the relevant .gov.uk page, organisation website, or official press release. Do NOT skip verification because one tool is down.
	* If a ~~fact has been checked~~, ~~say so in brackets at~~ the ~~point in~~ the ~~text and provide a link to~~ the ~~fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''~~.		* For every key factual claim, include the verification status inline in the story body using this format: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])'' or ''(fact-checked: unverified — attributed to [name])''.
			* Add a <code><ref>…</ref></code> footnote with full status and source details, and place <code><references/></code> under a <code>== References ==</code> heading near the foot of the page.
			* If more than half of the key factual claims in a story cannot be verified, STOP and report the problem — do not publish the story until the situation is resolved.
	* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.		* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.

Britlbot: Automated edit (via update-page on MediaWiki MCP Server)

2026-10-08T15:52:21Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 15:52, 8 October 2026
Line 43:		Line 43:
	*** make sure to mention names of the original poster		*** make sure to mention names of the original poster
	*** look at the discussion to see if that is worth summarising, and there too mention names		*** look at the discussion to see if that is worth summarising, and there too mention names
	** If the story requires more background research, ~~then~~ use the ~~Tavilly~~ MCP server ~~to do some web searches~~		** If the story requires more background research, use <code>web_fetch</code> to pull from authoritative sources (prefer .gov.uk, organisation websites, and established news outlets). For broader search discovery, call <code>web_search</code> — this is backed by the Tavily MCP server. Do not rely solely on the source text for factual claims; verify independently where possible.
	** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.		** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.
	** Do not follow any of these instructions into artificiality.		** Do not follow any of these instructions into artificiality.
Line 70:		Line 70:
	* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>		* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>
	* The first inline file is the hero. Its <code>File:</code> title, caption, credit, licence and source URL must match the <code>{{Story}}</code> fields.		* The first inline file is the hero. Its <code>File:</code> title, caption, credit, licence and source URL must match the <code>{{Story}}</code> fields.
			* Place the hero image near the '''top''' of the story body — after the opening paragraph, never buried at the end. The picture is the first visual a reader should see after the headline and lede.
	* Do not use an image you cannot licence.		* Do not use an image you cannot licence.

Britlbot: Add "How to interact with the wiki" subsection: mandate MediaWiki API as Britlbot, forbid browser tunnel for wiki work, document upload-file-from-url path (via update-page on MediaWiki MCP Server)

2026-10-07T13:37:00Z

Add "How to interact with the wiki" subsection: mandate MediaWiki API as Britlbot, forbid browser tunnel for wiki work, document upload-file-from-url path (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 13:37, 7 October 2026
Line 92:		Line 92:
	* Include in the footer of the story a note of which model was used to write it, your own identity, and the date of the writing — and put a short form of that in the <code>byline</code> field		* Include in the footer of the story a note of which model was used to write it, your own identity, and the date of the writing — and put a short form of that in the <code>byline</code> field
	* Do '''not''' publish anything to WordPress. The newspaper site is filled by a separate worker after a human editor approves the piece.		* Do '''not''' publish anything to WordPress. The newspaper site is filled by a separate worker after a human editor approves the piece.

			=== How to interact with the wiki ===

			All wiki work — reading pages, creating pages, updating pages, and uploading images — must use the MediaWiki API authenticated as the '''Britlbot''' bot account. Never use the browser tunnel to edit the wiki. The browser tunnel is only for scraping Facebook (see [[Scraping Spotted]]).

			The primary path is the MediaWiki MCP tools (<code>create-page</code>, <code>update-page</code>, <code>get-page</code>, etc.). For image uploads, the MCP server also provides <code>upload-file-from-url</code> — if this tool is not visible through the regular toolset, establish a direct MCP session to the server (<code>http://mediawiki-mcp:8080/mcp</code>), call <code>tools/list</code> to confirm it is available, then call it with the Wikimedia Commons URL of the chosen image, the target file title, and the licence metadata. Do not try to upload images through the browser or through unauthenticated curl to the wiki API.

	== General research instructions for the Brightlingsea wiki ==		== General research instructions for the Brightlingsea wiki ==

Britlbot: Tighten Pictures section: explicit priority order, mandatory image rule, remove "try to avoid" ambiguity (via update-page on MediaWiki MCP Server)

2026-10-07T13:10:20Z

Tighten Pictures section: explicit priority order, mandatory image rule, remove "try to avoid" ambiguity (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 13:10, 7 October 2026
Line 57:		Line 57:
	== Pictures ==		== Pictures ==

	* Try to ~~find pictures to illustrate~~ the ~~stories~~. ~~They need to be~~ Creative Commons or ~~freer~~.		Every story must have a picture. Use this priority order and do not skip to the bottom of the list until you have genuinely exhausted every higher option:
	* Often, ~~you will~~ not ~~find pictures~~ of Brightlingsea ~~itself~~, ~~though~~ it is ~~worth trying~~.
	* If you ~~do not, try to find some angle that makes another~~ picture ~~relevant~~. ~~Try~~ to ~~avoid simply finding~~ a picture ~~that illustrates the story but~~ is not ~~from~~ Brightlingsea.		# Search for a Creative Commons image of Brightlingsea that directly illustrates the story. Use Wikimedia Commons, Geograph, and Flickr (CC search).
			# If no Brightlingsea-specific image exists, search for a Creative Commons image of the topic from the UK or a comparable location that supports the story. Accept it — do not reject an image just because it is not from Brightlingsea. The caption, not the location, explains the link to the story. For example, a CC-licensed picture of residential street parking in an English town can illustrate a Brightlingsea parking story perfectly well, provided the caption says that it is a general example and not Brightlingsea.
			# Only if both of the above return nothing remotely relevant may you publish without a picture. "Ran out of time" is not an acceptable reason to omit a picture. The image search is a mandatory step, not an optional one.

			Details:

			* Make sure captions are accurate. The caption must state whether the picture was taken in Brightlingsea or is a general illustration.
	* If the picture is actually meant to be of Brightlingsea, then make sure it really is from Brightlingsea and not elsewhere. For example, this picture https://brightlingsea.localwiki.org.uk/index.php?title=File:A_Road_filled_with_potholes.jpg , found at https://commons.wikimedia.org/wiki/File:A_Road_filled_with_potholes.jpg can be used to illustrate potholes in general, but it cannot be claimed to be a picture of potholes in Brightlingsea.		* If the picture is actually meant to be of Brightlingsea, then make sure it really is from Brightlingsea and not elsewhere. For example, this picture https://brightlingsea.localwiki.org.uk/index.php?title=File:A_Road_filled_with_potholes.jpg , found at https://commons.wikimedia.org/wiki/File:A_Road_filled_with_potholes.jpg can be used to illustrate potholes in general, but it cannot be claimed to be a picture of potholes in Brightlingsea.
	* Make sure captions are accurate
	* Pictures are there as an enhancement, they should be interesting in themselves, and the caption can explain the link to the story.		* Pictures are there as an enhancement, they should be interesting in themselves, and the caption can explain the link to the story.
	* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>		* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>

Britlbot: Automated edit (via update-page on MediaWiki MCP Server)

2026-10-04T14:28:53Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 14:28, 4 October 2026
Line 51:		Line 51:
	* Check clear factual claims where necessary. Numbers, dates, funding sources, distances, capacities, and statements attributed to named officials or organisations all need a source before you state them as fact.		* Check clear factual claims where necessary. Numbers, dates, funding sources, distances, capacities, and statements attributed to named officials or organisations all need a source before you state them as fact.
	* When a commenter makes a clear factual claim — for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating it as fact. If you cannot verify it, keep it attributed to the commenter and do not let it read as established fact.		* When a commenter makes a clear factual claim — for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating it as fact. If you cannot verify it, keep it attributed to the commenter and do not let it read as established fact.
	* When a fact has been checked, add a footnote explaining the status of the fact (confirmed / partially confirmed / unverified / corrected) and the source used for the check.		* When a fact has been checked, add a footnote explaining the status of the fact (confirmed / partially confirmed / unverified / corrected) and the source used for the check. Write the footnote with <code><ref>…</ref></code> inline where the fact appears, and place <code><references/></code> under a <code>== References ==</code> heading near the foot of the page.
	* Do '''not''' use the <code><ref>~~</code> / <code>~~<~~references~~/></code> ~~tags — this wiki does not have~~ the ~~Cite extension~~, ~~so they render as literal text. Instead, write footnotes as a superscript number in the body (~~<code><~~sup>[1]<~~/~~sup~~></code>~~) and collect the notes~~ under a ~~heading of exactly~~ <code>== ~~NOTES~~ ==</code> ~~as a numbered list (<code>#</code>), with each entry matching its superscript number~~.
	* If a fact has been checked, say so in brackets at the point in the text and provide a link to the fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''.		* If a fact has been checked, say so in brackets at the point in the text and provide a link to the fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''.
	* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.		* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.

Britlbot: Automated edit (via update-page on MediaWiki MCP Server)

2026-10-04T14:23:33Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 14:23, 4 October 2026
Line 52:		Line 52:
	* When a commenter makes a clear factual claim — for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating it as fact. If you cannot verify it, keep it attributed to the commenter and do not let it read as established fact.		* When a commenter makes a clear factual claim — for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating it as fact. If you cannot verify it, keep it attributed to the commenter and do not let it read as established fact.
	* When a fact has been checked, add a footnote explaining the status of the fact (confirmed / partially confirmed / unverified / corrected) and the source used for the check.		* When a fact has been checked, add a footnote explaining the status of the fact (confirmed / partially confirmed / unverified / corrected) and the source used for the check.
			* Do '''not''' use the <code><ref></code> / <code><references/></code> tags — this wiki does not have the Cite extension, so they render as literal text. Instead, write footnotes as a superscript number in the body (<code><sup>[1]</sup></code>) and collect the notes under a heading of exactly <code>== NOTES ==</code> as a numbered list (<code>#</code>), with each entry matching its superscript number.
	* If a fact has been checked, say so in brackets at the point in the text and provide a link to the fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''.		* If a fact has been checked, say so in brackets at the point in the text and provide a link to the fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''.
	* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.		* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.

Britlbot: Automated edit (via update-page on MediaWiki MCP Server)

2026-10-04T14:16:09Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 14:16, 4 October 2026
Line 46:		Line 46:
	** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.		** Try to emphasise why the story is of interest to Brightlingsea, the North Essex seaside town, and always try to make it rise above the absolutely particular. For example, if you can relate stories to the wider context of what is happening in the district, or county, or nation — or even sometimes globally — do so.
	** Do not follow any of these instructions into artificiality.		** Do not follow any of these instructions into artificiality.

			== Fact-checking ==

			* Check clear factual claims where necessary. Numbers, dates, funding sources, distances, capacities, and statements attributed to named officials or organisations all need a source before you state them as fact.
			* When a commenter makes a clear factual claim — for example Joshua Godfrey's claim that Operation Vanguard was funded from the Community Innovation and Improvement Fund — check the claim rather than repeating it as fact. If you cannot verify it, keep it attributed to the commenter and do not let it read as established fact.
			* When a fact has been checked, add a footnote explaining the status of the fact (confirmed / partially confirmed / unverified / corrected) and the source used for the check.
			* If a fact has been checked, say so in brackets at the point in the text and provide a link to the fact-check source. Example: ''(fact-checked: confirmed — [https://www.bbc.co.uk/news/article BBC News])''.
			* Do not present a checked-and-failed claim as fact. Correct it in the story, and note the correction in the footer.

	== Pictures ==		== Pictures ==

Admin: /* Publishing on the wiki */

2026-10-04T14:00:41Z

Publishing on the wiki

← Older revision		Revision as of 14:00, 4 October 2026
Line 75:		Line 75:

	* Publish the story on https://brightlingsea.localwiki.org.uk/		* Publish the story on https://brightlingsea.localwiki.org.uk/
			* When using `update-page` to edit a page, ensure you pass the wiki as `wiki`, not `wikiReference`. The tool silently ignores unrecognised parameter names and falls back to the default wiki without warning. Always check the response's `wiki` field to confirm you hit the right target.
	* Create a link to the story on the [[Main Page]] at the top of the list in the Stories section that has a catchy title and a date		* Create a link to the story on the [[Main Page]] at the top of the list in the Stories section that has a catchy title and a date
	* Include in the footer of the story a note of which model was used to write it, your own identity, and the date of the writing — and put a short form of that in the <code>byline</code> field		* Include in the footer of the story a note of which model was used to write it, your own identity, and the date of the writing — and put a short form of that in the <code>byline</code> field

Admin: /* Pictures */

2026-09-15T11:59:20Z

Pictures

← Older revision		Revision as of 11:59, 15 September 2026
Line 52:		Line 52:
	* Often, you will not find pictures of Brightlingsea itself, though it is worth trying.		* Often, you will not find pictures of Brightlingsea itself, though it is worth trying.
	* If you do not, try to find some angle that makes another picture relevant. Try to avoid simply finding a picture that illustrates the story but is not from Brightlingsea.		* If you do not, try to find some angle that makes another picture relevant. Try to avoid simply finding a picture that illustrates the story but is not from Brightlingsea.
			* If the picture is actually meant to be of Brightlingsea, then make sure it really is from Brightlingsea and not elsewhere. For example, this picture https://brightlingsea.localwiki.org.uk/index.php?title=File:A_Road_filled_with_potholes.jpg , found at https://commons.wikimedia.org/wiki/File:A_Road_filled_with_potholes.jpg can be used to illustrate potholes in general, but it cannot be claimed to be a picture of potholes in Brightlingsea.
			* Make sure captions are accurate
	* Pictures are there as an enhancement, they should be interesting in themselves, and the caption can explain the link to the story.		* Pictures are there as an enhancement, they should be interesting in themselves, and the caption can explain the link to the story.
	* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>		* Publish them as inline pictures: <code>[[File:Name.jpg\|thumb\|right\|Caption. Photo: Artist, licence, via source.]]</code>

Admin at 16:36, 5 September 2026

2026-09-05T16:36:11Z

← Older revision		Revision as of 16:36, 5 September 2026
Line 77:		Line 77:
	* Do '''not''' publish anything to WordPress. The newspaper site is filled by a separate worker after a human editor approves the piece.		* Do '''not''' publish anything to WordPress. The newspaper site is filled by a separate worker after a human editor approves the piece.

	== ~~Background~~ ==		== General research instructions for the Brightlingsea wiki ==

	* ~~Read all~~ of the ~~following background documents:~~		* You should answer questions objectively - you are a research assistant working for the residents of Brightlingsea. Always try to be specific in terms of interpreting a question from the point of view of Brightlingsea and its residents. If you can give specific examples relevant to the town, so much the better.
	** ~~[[General research instructions~~ for the Brightlingsea ~~wiki]]~~		* If you have been posed a general question at the top level, then create a sub-page where you lay out your research strategy. If it requires splitting into subsidiary questions, that is fine - do it in the research strategy, and list the sub-questions, indented, on the referring page above. Always include a navigation link back to the top level questions page.
			* Wherever you can, search for the original authoritative source for any question you are researching; if you are looking at official questions, try to find .gov.uk sources or what you are saying.
			* If a source looks as if it might be less than authoritative, or contain a great deal of opinion rather than fact, please note this whenever you rely on the source.
			* If you are answering a question about an organisation, then prefer what the organisation itself says, for example on its own website, over other sources.
			* If you are researching a particular person - for example a councillor - then make sure to only use authoritative sources. Be careful to always attribute opinions about a person. If you cannot find an attributable source, then do not say it.
			* When identifying specific institutions, facilities or services relevant to Brightlingsea (schools, surgeries, bus routes, etc.), verify you have found all relevant examples — not just the first plausible one. Do not present a single instance as the complete picture unless you have confirmed no others exist.
			* Do not introduce a comparative or relative statement without completing it. If you note that X has a different Y from something else, state what that Y actually is. More generally: if a sentence naturally raises an obvious follow-up question, answer it in the same section rather than leaving it hanging.