Reader impact before jargon
Public records are translated around who is affected, what changed, what deadline matters and where the original source can be checked.
Open Plain EnglishEditorial standards · public trust
How Moghrey Mie keeps the briefing useful and checkable.
A reader-facing standards page for plain-English summaries, source handling, corrections, commercial disclosure, public-record scope and daily verification. It explains the rules without exposing private account or workflow data.
Core editorial standards
These are the promises a reader should be able to see in the website structure, not only in internal notes.
Keep original routes close
Stories, public notices, FOI items, Tynwald papers and tenders should keep source names or links visible whenever issue data provides them.
Open Source trailMake fixes easy to send
Broken links, unclear summaries, dates, names or factual issues should have an obvious correction route tied to the page or issue URL.
Open CorrectionsLabel paid and affiliate surfaces
Advertising and product links stay separated from editorial source notes, with disclosure before readers leave the site.
Open Commercial boundaryPublic operating checklist
The static site should keep quality and safety boundaries visible for readers, sources and advertisers.
- Public-record scopeTynwald, government, FOI, tenders, consultations, court/public notices, events, weather and tides are handled as checkable public-interest material.
- No private-data promisesSubscriber data, credentials, private dashboards, analytics accounts and provider settings do not belong on public website routes.
- Daily verificationThe build, smoke, publish and live-check path should leave proof before a website slice is called shipped.
- Readable routesA reader should be able to find Today, Latest, Archive, Sources, Corrections, Tips, Subscribe and Advertising without decoding internal workflow language.
Where to verify or challenge it
Each standards claim points to a practical route.
- Sources/sources/ · See source handling - Public source model, latest issue examples and correction route.
- Coverage/coverage/ · Check what belongs - Briefing scope, topic routes and public-record boundaries.
- Corrections/corrections/ · Send a factual fix - Broken links, unclear summaries, wrong dates or missing context.
- Status/status/ · Check publish proof - Latest issue, send marker, website marker and generated routes.
Found something that does not meet the standard?
Send the issue URL, the problem and any public source evidence so the archive can be checked and corrected.