Provenance

A record has a stable identity. Its definition, properties, explanatory assertions, and relationships are represented as claims with stable identifiers within that record.

A sourced claim

The claim supplies its subject, value, assumptions, source identifier, and a locator such as a theorem, section, named table, or field. The source page links back to every dependent assertion. This supports checking an individual fact rather than relying on an undifferentiated bibliography.

Open SU(3), expand a claim, and follow its locator. A source page shows the reverse dependency.

A derived claim

A derived claim names a method and its premises. Premises may reference existing entities, existing claims, sources, or explicit literal inputs. The catalogue validator rejects unresolved entity or claim references. A derivation recorded as prose is not automatically an executable algorithm.

What automatic validation establishes

Build-time checks enforce the schema, unique identifiers, typed relationships, source references, exact decimal finite orders, and capability links. Complete finite irrep summaries additionally pass degree-square, reality-parity, and conjugate-pair consistency checks. Independent fixtures exercise the implemented calculators and convention-sensitive reference cases.

These checks catch particular classes of mistakes. They do not prove every statement in a source or replace expert review.

Review and change

Each record has a SHA-256 fingerprint covering its scientific content, evidence, convention-relevant data, capability definitions, versions, and applicable mathematical-engine code. Approvals must match the current fingerprint. Review history distinguishes current decisions from stale ones.

The review queue gives the current state. Prepare a correction when an assertion, source locator, convention, or physical interpretation needs attention.