Reference guide · checked 2 September 2026

How this cross-reference is verified

Battery Codebook derives a relationship from independently recorded fields. It does not import a competitor’s finished table or convert every observed alias into an indexable page.

Evidence hierarchy

Current manufacturer datasheets and selection guides are preferred for identity, dimensions, voltage, chemistry and drain designation. Official public authorities control safety routes. Secondary commercial tables may reveal a question worth checking, but they do not become the factual source.

Each record stores publisher, document title, URL, location, checked date, confidence and reuse restriction. Conflicts remain visible until a reviewer can resolve them.

Canonical families

Aliases supported by evidence resolve to one record. Relationships between records are classified separately as exact, conditional, same-diameter/different-height or incompatible. This prevents LR44/A76 alias handling from being confused with the conditional relationships to SR44SW/303 and SR44W/357.

Corrections and maintenance

Sources are rechecked on a scheduled cycle and sooner when a correction identifies a material problem. A checked date changes after factual review, not merely after a layout edit. A correction should identify the page, disputed field and primary evidence.

  • Resolve identity.
  • Verify physical fields.
  • Verify voltage and chemistry.
  • Verify drain designation.
  • Assign and review the relationship verdict.

From claim to ledger

A record begins as individual claims: designation, alias, diameter, height, nominal voltage, chemistry and drain category. Each claim is tied to a publisher, title, URL, document location, checked date, reviewer confidence and restriction note.

This makes it possible to correct one field without silently rewriting unrelated records. It also exposes when a guide supports aliases but not a universal capacity.

From fields to relationship

Exact identity is established before compatibility. Different records are then compared at the physical, electrical, chemistry and drain gates. The displayed rationale is generated from those differences and manually reviewed for the curated pair.

Arbitrary pair URLs are not published. A dedicated comparison exists only where genuine confusion warrants standalone analysis.

Handling disagreement and change

When current primary sources disagree, the record should describe the conflict, narrow the claim or remain unpublished. Confidence is not a substitute for resolving a safety-relevant contradiction.

Scheduled review checks links and current documents; substantive re-verification updates the checked date. Design edits, automated rebuilds and deployment dates do not.

Publication checklist

Before a record or comparison is accepted, confirm that every material field has a current primary route, a checked date and a confidence level. Verify that aliases share a canonical identity, while alternatives remain relationship edges. Review the displayed rationale, safety wording, internal links and indexation state, then record unresolved conflicts rather than concealing them.

  • No copied table structure or prose.
  • No alias or arbitrary-pair pages.
  • No unsupported capacity generalisation.
  • No publication while a safety-relevant conflict remains.