Reyn Studio documentation
Model bundles, signatures, and qualification
Learn what the authenticated research bundles prove and what remains unqualified.
Understand Reyn model bundle formats, signature meaning, support gates, and the bundled H64 and 32³ research-preview models.
Authenticated research models are bundled
The 2D benchmark results apply strictly to the 2D multi-shape study; 3D CAD Run uses the separate signed 32³ one-jump obstacle operator (RelL2 0.052 at 128 steps, 32,768 cells) bundled in the macOS, Windows, and Linux 0.4.1 archives.
What a production model set contains
- A .reynmodel bundle with Safetensors weights and a canonical manifest.
- A detached .reynmodel.sig signature artifact.
- Offline TUF metadata under a matching .reynmodel.tuf directory.
- A declared model identity, architecture, channels, grid, physics scenario, horizon, and support envelope.
- Immutable benchmark and calibration evidence bound to the exact model hash.
Pickle-backed .pth, .pt, and .ckpt files are not accepted by the production app path.
What signatures and hashes mean
- SHA-256 identifies bytes and detects modification. It does not identify the publisher.
- A valid signature proves possession of the signing key and binds the signed payload.
- A trusted fingerprint must be compared through an independent channel.
- A valid signature does not prove that the model is accurate or suitable for a case.
- Scientific qualification still requires sealed held-out evaluation, support-envelope checks, app smoke tests, and release approval.
Request beta credentials.
All documentation and packages are public; approved beta credentials unlock the desktop application.