How the reference is reviewed

The reference connects precise mathematical objects to supported calculations. A useful entry identifies its subject, states its assumptions, supplies evidence, and makes its limits visible.

Coverage and review answer different questions

Classification means an entry identifies an object or family and its scope. Reference means specified properties have been curated. Executable means named calculations are available over a stated domain. These labels describe what an entry contains.

The review record describes how that content has been checked. Sources, automated consistency checks, and human expert review each supply different evidence. The foundation release uses AI-assisted source curation and automated checks; independent expert review remains pending. A source link or a passing test alone does not confer an expert-reviewed label.

Evidence belongs to the claim

A mathematical claim should identify its subject, value, assumptions, source and precise locator, or an explicit derivation. Claims about dimensions, centers, representations, and topology must retain their applicable field, global form, category, and conventions. Linked upstream resources remain identifiable sources rather than unnamed authority.

Automated checks examine identities, references, supported domains, and selected independent mathematical fixtures. Their results have a declared scope. A dimension check, for example, is evidence of one necessary condition for a branching rule.

Review the exact revision

Contributor review uses three operations: inspect review status, request review, and record a review. A human review records the reviewer’s name, mathematics or physics role, verdict, explanatory note, and the content fingerprint under review. A changed fingerprint makes an earlier review stale.

An executable capability requires approving reviews from two distinct named people, covering mathematics and physical interpretation, before it can be described as expert-reviewed. Reviewers should examine conventions, exceptional cases, source support, and failure behavior as well as representative outputs.

Changes to claims or calculations belong in the versioned record and release history. Report a specific problem through the correction workflow; retain the affected version when citing a result, as described in reproducibility.