Signed and verifiable
Every archive is paired with a signed release document carrying its identity and content digest. Consumers verify both offline — no registry call and no trust in the download path.
Skip to content
v0.6.1 · schema v1
Scrollcase
Pack AI and scientific models
as self-contained boxes.
Pinned, validated, signed, no Docker, and usable offline on macOS Metal, Linux and Windows (CPU and CUDA).
Licence: Apache-2.0
No container runtime
A box is a single archive that unpacks into a self-contained Python environment. No Docker, no daemon, no dependency resolution at install time.
One format, many targets
macOS Metal, Linux and Windows on CPU or CUDA — described by one target model that builders, signers, and clients agree on character for character.
A scroll for all your spells
Resolve, build, validate, sign — one pipeline, one format, every target.
Build from a scroll.json
Describe the environment once. Scrollcase resolves it against conda-forge with pixi and produces a box per target, fully pinned.
Validated before shipping
Every build checks target and imports; scrolls can add Python assertions, required files, and numerical parity gates. A failed gate produces no box.
Accelerator-aware
The accelerator and CUDA ABI version are part of the box identity, so a CUDA 12.4 build can never be mistaken for a 12.8 one.
Reproducible identity
The target ID used in archive names and object paths is derived deterministically and locked by golden fixtures.
Portable contract
The box format ships as a reference implementation plus JSON Schemas and fixtures, so other languages can mirror it and stay in agreement.
Air-gapped installs
Download once, carry the archive across, verify and unpack anywhere. The same box works on a connected laptop and an isolated workstation.
Core CLI Commands
Seven focused verbs, plus public modules for consumers and integrations.
initdoctorkeygenlockauditbuildverifyscrollcase/contractscrollcase/buildscrollcase/signscrollcase/contract/typesScrollcase stops at a signed, verified box on disk. Distribution, promotion, registries, and installation policy belong to the consuming project.