Editorial Methodology

BLE applies this hierarchy when reviewing bibliographic and relationship data:

1. Official publisher, product, editorial, and edition material from Black Library or Games Workshop.
2. Library catalogues, bibliographic catalogues, and retailer records as secondary evidence when official material is incomplete or unavailable.
3. Community sources only as discovery leads that must be checked against stronger evidence before they support a published fact.

The sources policy explains what each category can support. Source prominence or search ranking does not override this hierarchy.

BLE records and connects data by hand in a structured graph. Editors use the available evidence when adding or correcting catalogue data, normalize presentation without changing the meaning of a source, and record only the specificity the evidence supports. Missing facts remain absent.

Entity detail pages present catalogue data without a per-field verification status. Editorial pages provide navigation and recommendations without public product-source records or claim-level citations. Their text must not be read as proof that every field in the underlying catalogue received an individual source review.

Official materials can disagree across product pages, formats, territories, or editions. BLE does not guess through unresolved conflicts. The editor compares the edition and publication context, prefers the most directly applicable official evidence, and leaves a value unresolved when the evidence does not support a defensible choice.

Corrections that identify a conflict are reviewed under the correction policy. A resolution should preserve the evidence and explain a material editorial choice rather than silently replacing one assertion with another.

Relationships are stored when a source states them or when the relationship is an explicit BLE editorial classification. Editorial reading orders are guidance, not publisher canon. They link to BLE catalogue pages rather than maintaining a second set of external product records.

Policy and editorial review dates are explicit content values. Git commit time, deployment time, backend maintenance time, and build time are not treated as evidence that a fact or article was reviewed.

• Coverage is intentionally limited to the project scope described on the About page.
• Some records are incomplete, and older or obscure editions may have sparse official metadata.
• Catalogue records do not expose per-field source coverage or verification status.
• Retailer and catalogue records can repeat publisher errors or omit edition context.
• Editorial relationships and reading orders can change when stronger evidence or a better-supported interpretation becomes available.