Skip to the field note
DecisionFieldbook Independent / non-affiliated
Evidence desk / public register

Every dated claim should show its boundary.

The strategy framework is original editorial analysis. Game context, historical identity, dates, and old URL records require public evidence. This page explains what each source is allowed to support and when a claim must be reviewed.

Decision trace
  1. 01ObserveRecord a public source and access date.
  2. 02NameState the exact claim it supports.
  3. 03CompareCorroborate history and resolve conflicts narrowly.
  4. 04CommitPublish the claim with a freshness class.
  5. 05ReviewRevise, narrow, or remove when evidence changes.
SOURCE 01

Authority is contextual, not a single score.

Use the right source for the right claim

Official Blizzard pages are the primary source for game rules, current first-party context, and Blizzard's own trademark guidance. They do not support claims about the former podcast. The Internet Archive supports the existence and visible dates of former public URLs. It does not prove present ownership, audience size, rights, or the accuracy of every sentence that once appeared on a page.

Podcast directories support limited catalog metadata such as title, episode number, display date, and publicly associated names. A directory is not treated as permission to reproduce a recording or description. Historical bridge facts require both an archived path and a separate directory record because either source alone can be incomplete.

A 2017 research-paper record is included to flag a similarly named Hearthstone coaching project. It supports only the existence and bibliographic identity of that paper. It is not evidence that the research project and the former podcast were connected. The register states this limited use so that a citation does not silently grow beyond its scope.

SOURCE 02

Last checked is a review date, not a guarantee of no change.

Four freshness classes

Evergreen pages teach original decision methods that do not depend on a current card pool or ranked environment. They are reviewed every 180 days and after a major rules-system change. Mixed pages add a small amount of current or historical context, so they are reviewed every 90 days and whenever a cited primary source changes.

Historical pages describe a closed public record and receive an annual review, plus an immediate review when better evidence or a correction request appears. Policy pages cover identity, rights, sources, privacy, and corrections. They receive a 180-day review and an immediate review after an operator or disclosure change.

Decision Fieldbook excludes live tier lists, current win rates, current keep percentages, prices, event schedules, and patch summaries. Those subjects require a faster editorial operation, methodology disclosure, and frequent expiry. Listing a dated official patch note establishes the freshness boundary; it does not turn this library into a live metagame source.

  • Evergreen: original reasoning framework, 180-day review.
  • Mixed: durable teaching plus dated context, 90-day review.
  • Historical: bounded public record, annual and evidence-triggered review.
  • Policy: identity, rights, source, and correction material, 180-day and change-triggered review.
SOURCE 03

Unknown is an acceptable and useful result.

Publish claim states, not false certainty

A supported claim is directly stated by a listed source or visible in an archived URL. A corroborated claim appears in at least two independent public records. An inferred claim is a narrow conclusion drawn from supported facts and must be labelled as inference in the prose. An unknown claim is not published as fact.

When evidence conflicts, use the smallest statement both records can support and describe the conflict if it materially affects meaning. Do not average incompatible dates, choose the more attractive title, or let a search snippet overrule an opened source. If the conflict prevents reliable identification of an old URL, the route remains 410.

A source can disappear. If a historical statement loses its only support, remove or quarantine that statement until another public record is found. Do not replace a broken citation with a source that merely repeats the same unsupported claim. The evidence boundary matters more than preserving the page's apparent completeness.

SOURCE 04

Privacy and impersonation concerns take priority over continuity.

Correct the claim, then the date

A useful correction identifies the page, the sentence or metadata field, and a public source that supports the change. The editor checks the source, changes only what the evidence justifies, updates the page's last-checked date, and records a material correction in a future public change note if one exists.

Requests involving personal information, false affiliation, impersonation, rights, or a bridge assigned to the wrong record receive priority. A bridge can be reduced to 410 while a question is reviewed. Removing a risky historical claim is preferable to preserving a backlink or a complete-looking sequence.

This local pilot contains no public submission form and collects no correction data. Any future publication must add a contact method only after the operator has defined privacy, retention, abuse handling, and response ownership. The absence of a form should not be filled with an invented address or borrowed identity.

PUBLIC REGISTER

Source records used by this package

The register states a limited use for every source. Opening a source does not make it a general endorsement of the library.

primary

Returning Player Guide

Blizzard Entertainment

Used for
Current official context that the live game changes over time
Accessed
2026-08-28
Freshness
Current-context source, not a basis for live strategy claims
primary

36.4 Patch Notes

Blizzard Entertainment

Used for
Freshness boundary and proof that patch-specific facts expire
Accessed
2026-08-28
Freshness
Point-in-time source dated 2026-08-24
research

HearthCoach: A coach for Hearthstone

IEEE Conference on Computational Intelligence and Games

Used for
Identity-collision warning only; not evidence about the former podcast
Accessed
2026-08-28
Freshness
Stable bibliographic record
NEXT FIELD NOTES

Continue with a purpose

  1. See the policy applied to history

    Read the supported timeline, route decisions, and explicit unknowns.

  2. Read the identity and rights boundary

    See how independence, trademarks, privacy, and assets are handled.

  3. Return to the original study library

    Use evergreen lessons that state their own review cadence.

EVIDENCE AND FRESHNESS

What this page depends on

Class
policy
Last checked
2026-08-28
Next review
2027-02-24
Basis
Policy page reviewed every 180 days and after any identity, rights, source, or correction-process change.