The Corrections Ledger.

Corrections to our own content · 5 entries

News wire: News wire: no corrections yet. The wire's corrections log (news-scanner/state/corrections.jsonl) does not exist because the scanner creates it only when the first correction or retraction is appended, and every item the wire tracks is still at version 1 (185 items in state/item_state.json, all version 1; all 13 rows of item_versions.jsonl are version 1; no item carries a retracted status). When the wire corrects or retracts an item, the entry lands in this ledger the same day.

2026-10-30 corr-0001

Discord — Strategies forum thread “Strategies: Darkspear Islands — what we know (and what we don't)” (thread/message 1565726541458055239)

Was

The thread announced the first guild battleground night as “Friday Nov 7, 18:00–21:00 PST”. The date and time were right; the weekday was wrong.

Now

Saturday Nov 7, 18:00–21:00 PST. November 7, 2026 is a Saturday.

Why

The Content Keeper's first audit (2026-10-30) checks every weekday name a surface prints against the real 2026 calendar, and Nov 7, 2026 falls on a Saturday. The Discord scheduled event for Battlegrounds Night (1565708619675209918, starting 2026-11-08T02:00:00Z — Nov 7, 18:00 PST) confirms the date itself was correct.

Source: ~/workspace/discord-guild-build/content-keeper/registry.json — entry thread-strategies-darkspear (weekday_dates check; last_verified 2026-10-30T14:19:55Z); pre-fix text captured in ~/workspace/discord-guild-build/mux/events.jsonl seq 82, 2026-10-30T13:58:16Z (message 1565726541458055239)

2026-10-30 corr-0002

Discord — #ask-thrall pinned intro (channel 1565687093315772469, message 1565687215462420501)

Was

The pinned intro said Ask Thrall answers from a corpus of 243 admitted facts.

Now

245 admitted facts.

Why

Two facts were admitted live (knowledge/facts-live.jsonl) on top of the 243-fact base corpus, taking the answered corpus to 245. The Content Keeper's cited_facts_count check requires every surface that cites the count to match the live corpus size, so the stale figure was drift the moment the second fact landed.

Source: ~/workspace/discord-guild-build/content-keeper/registry.json — entry discord-ask-thrall-intro (cited_facts_count check; dependencies_at_verify facts_count: 245; last_verified 2026-10-30T14:19:55Z); ~/workspace/rise-site/placements/README.md (“245 admitted facts (243 base + 2 live-admitted)”)

2026-10-30 corr-0003

Guild placement / listing drafts — ~/workspace/rise-site/placements/ (DISBOARD, discord.me, top.gg, r/wowguilds and Blizzard forums drafts, and the pack README)

Was

Draft copy cited “four hundred thirty-two admitted facts” for the Ask Thrall corpus.

Now

245 admitted facts (243 base + 2 live-admitted), matching the live corpus. The keeper's checker now treats the old combined figure (and the stale base-only count) as stale strings and fails any surface that carries them.

Why

The combined figure was never the admitted count: the placements pack itself records 243 base facts plus 189 further eligible, source-linked claims held in the Tier-1B evidence ledger (243 + 189) — eligible is not admitted. Only the 245 admitted facts are what Ask Thrall answers from, so only 245 may be printed.

Source: ~/workspace/discord-guild-build/content-keeper/check.py (stale-figure scan — the old combined figure and the base-only count); ~/workspace/discord-guild-build/content-keeper/registry.json — listing-draft-* entries (cited_facts_count checks; dependencies_at_verify facts_count: 245); ~/workspace/rise-site/placements/README.md (243 base + 2 live-admitted + 189 eligible Tier-1B claims)

2026-10-30 corr-0004

Discord — Start Here index post (channel 1565682332034142238, message 1565687115138736139)

Was

The post said in-game guild chat “syncs straight into” the #guild-chat Discord channel, stated as settled fact.

Now

The claim is hedged. The exact phrase “syncs straight into” is now a forbidden string in the Content Keeper's checks for this post, and the companion Guild Chat — Battle.net Link post (message 1565687196974059552) is required to carry the words “not yet officially confirmed”.

Why

Linked Guild Chat availability in WoW: Forever is unconfirmed — the corpus carries it at the unknown tier and Blizzard has published nothing that settles it. An un-hedged sync claim promised members a feature nobody has verified exists.

Source: ~/workspace/discord-guild-build/content-keeper/registry.json — entries discord-start-here-index (forbidden: “syncs straight into”; dependency note: Linked Guild Chat availability unconfirmed) and discord-guildchat-battlenet-post (required: “not yet officially confirmed”), both last_verified 2026-10-30; corpus fact wf-0194 (unknown tier), via ~/workspace/research_notes/rise-beat-wowhead-research-20261030/report.md §7 U6

2026-10-30 corr-0007

Rise website (riseguild.vercel.app) — header tagline and page titles — and Discord — server description, launch announcement (#announcements, message 1565687162697941043), and recruitment how-to (#recruitment, message 1565687229970387090)

Was

The site's header tagline read “HORDE · PVP · FOREVER”, and page titles and copy presented Rise as a “Horde PvP Guild” and “PvP-first”. The Discord server description, launch announcement, and recruitment post carried the same framing — together they described a PvP-only guild.

Now

Rise is a full-spectrum Horde guild — leveling, dungeons, raids, and PvP — on the PvP ruleset. The ruleset is where we play, not all we are. The website header and titles, the Discord server description, the launch announcement, and the recruitment copy were all corrected to the full-spectrum framing on 2026-10-30.

Why

The guild's owner corrected the positioning directly: Rise was never a PvP-only or PvP-first guild. Leveling, dungeons, and raids (from the December 9 unlock) are first-class pillars alongside battlegrounds and world PvP; the PvP ruleset names the server we play on, not the whole of what the guild does. Our own copy had narrowed the guild to one pillar, which misstates who we are to every recruit who reads either surface.

Source: Owner positioning directive, 2026-10-30; audit inventory ~/workspace/discord-guild-build/positioning-audit/surfaces.json (Discord surfaces corrected and read back the same day); website copy corrected in deploy dpl_JyUKnE9dUdfU1TYyuQ9W31sKcKer

Field watch — errors we've tracked elsewhere, not our content · 2 entries

2026-10-30 corr-0005

Icy Veins — WoW: Forever Collector's Edition pre-purchase article (not our content)

Was

The article states the Collector's Edition statue is 13 inches tall. Checked on 2026-10-30, it still said 13 inches — at least 8 days after a dated public correction existed (Oct 22, 2026) and roughly seven weeks after the article was published.

Now

Blizzard's own product page (Blizzard Gear — gear.blizzard.com) says the statue is 7.5 inches (verified 2026-10-30), and a retailer listing (JB Hi-Fi NZ) agrees. The 13-inch figure traces back to Blizzard's original globally supplied specs, which were themselves wrong.

Why

The current retail primary source (Blizzard's own Gear page) governs over secondary republication. Our corpus keeps both values with provenance — 13 in (wf-0021, community) and 7.5 in (wf-0022, Blizzard Gear) — because the wrong value came from the primary source's own first spec sheet; final settlement is physical, when units ship (Feb 2027 per retailer notes).

Source: ~/workspace/research_notes/rise-beat-wowhead-research-20261030/report.md §4 Q2 and §6 C1 (Icy Veins article crawled live 2026-10-30; Blizzard Gear page (gear.blizzard.com) verified 2026-10-30; dated third-party correction Oct 22, 2026)

2026-10-30 corr-0006

Icy Veins — Skyborne racials article, Oct 29, 2026 (not our content)

Was

The article — the freshest big-site treatment of the Skyborne racials — publishes a third set of values that matches neither Blizzard's published set nor the reported final beta tuning: Wind Blessed at 3% (neither source says 3%) and Skysight at +10%. Its Walk on Air cooldown (1.5 min) matches the tuning report, so the page reads as one coherent set while blending two different builds.

Now

No single authoritative set exists before launch. On record: Blizzard's Sep 22 published set (corpus wf-0094, official — Walk on Air glide 10s, Wind Blessed haste, Elemental Insight +5% vs elementals) and the reported Oct 26 final beta tuning (wf-0095, secondary — Wind Blessed 2%, Walk on Air 90s cooldown, Skysight +15% speed / +30% Charged). The values settle when the live client can be read on Nov 4.

Why

Three builds produced three number sets during beta. A single-number page cannot say that, so it silently merged them. The honest pre-launch answer is both sets, with provenance, flagged as unsettled — which is the form our corpus holds the pair in.

Source: ~/workspace/research_notes/rise-beat-wowhead-research-20261030/report.md §4 Q4 and §6 C2 (Icy Veins article dated Oct 29, 2026, checked 2026-10-30; corpus facts wf-0094 / wf-0095)