Data interface

This edition exposes static reference resources and locally executed calculators. It does not provide a general remote computation API.

Available resources

• /data/catalogue.json: validated records, claims, sources, and capabilities.
• /data/claims.json and /data/sources.json: assertions and bibliography.
• /data/entities/{kind}--{slug}.json: a record, its claims, relevant sources, versions, and review state.
• /data/conventions.json: the ten versioned convention profiles.
• /data/model-setups.json: an index of three worked, loadable model-calculation/1 files.
• /data/physical-setups.json: an index of eleven worked physical-setup/1 and physical-calculation/1 files.
• /data/physical-setup.schema.json: the physical input contract.
• /data/operator-inventories.json: six worked enumeration inventories and result files.
• /data/operator-inventories/{id}.json and /data/operator-enumerations/{id}.json: inputs and recomputable result envelopes.
• /data/operator-enumeration.schema.json: the inventory, range, identity, and charge-selection contract.
• /data/root-systems.json: numbered root data and positive coroots for the 32 supported types and ranks.
• /data/characters/{id}.json: complete exact character tables, for c3, s3, d8, q8, a4, s4, and a5.
• /data/workbench-methods.json: operation scopes, bounds, versions, and method metadata.
• /data/review-status.json: fingerprints and review states.
• /data/release.json: edition versions, counts, and canonical routes.

For example, SU(3) JSON corresponds to its canonical group page. The A₅ table is a computational character-table resource and retains its own class and field conventions.

Interpretation contract

Read schema and version fields before interpreting a payload. Decimal-string integers, numerator/denominator pairs, and exact character-field coefficients must remain exact until a consumer deliberately requests a numerical approximation. Bounded structural metadata such as rank, node index, and checked input labels may be JSON numbers.

A convention profile is identified by both its stable ID and version. The Cartan matrix fixes the root-label order. Character-table columns require their named class representatives and power maps. A branching result requires the exact homomorphism, including its kernel and image. No unsupported operation becomes supported merely because its group has a catalogue entry.

Reproduction and corrections

Access follows the site’s audience. Use downloaded snapshots for local notebook work and retain dataset and claim IDs in derived data. A calculator link restores inputs with the current engine; its JSON export preserves the computed result and specific versions. Include that record in an evidence-backed correction packet when reporting a discrepancy.