Reference#
Organized by the question you arrive with: what you call, what a record of each type looks like, what records emit semantically, what the infrastructure promises, and what is supported today. The generated pages are produced from the code, schemas, and mapping tables and drift-checked in CI, so they cannot rot.
What you call#
The two generated surfaces: the Python API and the CLI. For the workspace, the everyday way most people author records, see the how-to guides.
Record types#
One page per record family, and each page is the whole story: what the thing is, a reference example (authoring code, the canonical record, its JSON-LD), and the field reference from the JSON Schemas. When someone asks how to describe a cell, a material, or a separator — the answer is one link.
What records emit#
The semantic layer: the property and unit vocabulary behind every quantity. For the anatomy of a published JSON-LD document, see Anatomy of a published BattINFO record (battinfo.json) (under Concepts).
Guarantees#
The three contracts on one page — infrastructure, validation, ingest manifest — each naming the reader it is for.
Status#
What is supported today, what is preview, and how well each external data source round-trips.