path stringclasses 5
values | size int64 1.26k 2.5k |
|---|---|
.gitattributes | 2,504 |
README.md | 1,874 |
job-2026-nemo-v3-governed-attempt-11/blocked_receipt.signed.json | 1,322 |
job-2026-nemo-v3-governed-attempt-13/blocked_receipt.signed.json | 1,321 |
job-2026-nemo-v3-governed-attempt-14/blocked_receipt.signed.json | 1,258 |
SZL Training Receipts
Private, append-only evidence store for governed owner-GPU attempts. This repository is not a training corpus, benchmark, model release, or proof that a queued job ran successfully.
Authority boundary
- Source controller:
szl-holdings/szl-gpu-bridge - Source revision:
22050da626709e7350512163cbe32f58de2d684f - Target:
SZLHOLDINGS/szl-training-receipts - Visibility: private
- Publication authority: the trusted finalizer after local signature, jobspec, queue-envelope, replay-barrier, and immutable-readback validation
The source controller verifies the exact job ID, queue payload hash, enrolled owner-laptop key ID, signature, evaluation fields, and no-publication boundary. A missing receipt remains missing evidence; it is never converted into success.
Expected record shape
Terminal records are stored under their exact governed job ID. The canonical validation and refusal logic lives in:
cloud/nemo_v3_status.pylaptop/finalize_nemo_v3_receipt.pylaptop/nemo_v3_contract.pyschema/nemo-v3-jobspec.v1.json
No record count is claimed in this card. Inspect the immutable repository revision and validate each receipt independently before relying on it.
License and data handling
license: other is deliberate. Receipt envelopes may contain governed
operational metadata and do not receive a blanket data-reuse grant. Model
weights, credentials, private keys, raw training rows, and secrets must never be
uploaded here.
Card completeness (2026-11-12)
This section adds required card sections the card above did not have. It states only what files in this repository and the estate's own receipt datasets show; nothing here is a new result.
Provenance
Not yet documented. As of 2026-11-12 the card has no provenance statement: who created this data, how it was collected or generated, from which sources, and what filtering was applied. The owner should add this before the dataset is relied on.
- Downloads last month
- 400