# Catalog schemas

The two JSONL files have separate Hugging Face configurations. Each line is one JSON object. Every field is a UTF-8 string, including `details_json`, which contains canonical serialized JSON. This keeps heterogeneous mathematical records faithful without forcing incompatible matrix and field encodings into a shared table schema.

## certificates.jsonl

| Field | Meaning |
|---|---|
| `id` | Stable release-local record identifier, e.g. C001. |
| `suite` | Generic control, short returns, extension fields, or worked examples. |
| `kind` | Case, suite summary, scope counterexample, or other certificate category. |
| `claim` | Concise description of what the cited finite record checks. |
| `source_path` | Original JSON file, relative to the repository root. |
| `source_pointer` | RFC 6901 JSON pointer; empty string selects the whole source object. |
| `arithmetic` | Exact arithmetic used by the cited record. |
| `status` | Recorded or derived execution status; not a priority or peer-review status. |
| `details_json` | The exact selected source value, serialized as JSON. |

Suite summaries include their constituent cases. Catalog rows must not be added together as independent experimental trials. In particular, the 300 transport comparisons and 6,104 replayed strokes are suite-level counts, not the number of JSONL rows.

## theorems.jsonl

| Field | Meaning |
|---|---|
| `id` | T1 through T5, matching the paper's theorem numbering. |
| `title` | The theorem's identifying name. |
| `statement` | Compact statement with the principal quantitative conclusion. |
| `assumptions` | Essential field, rank, and palette hypotheses. |
| `scope` | Interpretation and limits, including one-spare and field distinctions. |
| `proof_path` | Repository path of the full paper source. |
| `proof_section` | Human-readable section containing the proof. |
| `status` | Proof/internal-audit status, explicitly separate from worldwide novelty. |

The theorem index is editorial metadata, not a formal proof-assistant library. The complete arguments remain in the paper. The certificates are finite exact computations, not a replacement for those arguments.

## Regeneration

From the repository root:

```bash
python tools/build_catalog.py
```

The builder reads only the frozen `repro/` records and writes the two catalogs deterministically. Updating any repository file also requires regenerating `MANIFEST.sha256` before using the uploader.