# Repository baseline This directory is a standalone Git repository on `main`. The initial snapshot includes source, vendored backends/assets, licenses, experiment recipes, manuals, tests, CI and dependency locks. No remote is configured or pushed automatically. Configure your actual hosting URL before pushing; do not reuse the reference project's remote. ## License Original code and documentation use Apache-2.0, following Jumper. The unmodified license text is in [LICENSE](../LICENSE); project attribution and third-party obligations are in [NOTICE.md](../NOTICE.md). Existing Apache/BSD/MIT vendor licenses remain intact. Package metadata uses the combined `Apache-2.0 AND BSD-3-Clause AND MIT` expression for the distribution, with license texts included in the wheel. ## Locks and CI - `uv.lock`: complete reference Linux CUDA dependency resolution, plus the lightweight CI group. - `requirements-linux-cu130.lock`: hashed pip export for the development/training environment. - `requirements-ci.lock`: hashed pip export for check/build tools only, without Torch/CUDA. - `.github/workflows/check.yml`: immutable action revisions, pinned uv, locked check/build tools, lock/export synchronization, vendor inventory, wheel parity, Ruff and core/layout tests. The CI job does not run GPU simulation. Hosted Actions only run after publication on GitHub; local reproduction is not a claim of a hosted green build. See [Setup](SETUP.md) for commands. ## Local verification The full configured environment passed **94 tests** and Ruff lint/format checks. A separate locked CI-only environment passed **77 tests, 3 skipped**; GPU/backend-dependent tests were intentionally skipped. Wheel parity checked **370 package files** plus **7 distribution license files** and the SPDX metadata expression. Both requirements exports were regenerated from the lock without drift. The staged snapshot was reviewed for generated files, symlinks, oversized files, personal workspace paths and common secret formats. `.venv*`, runs, logs, bundles, build output, caches, checkpoints, `.env` variants and private-key files are excluded. This screening is not a guarantee that no possible sensitive information exists; review changes before publishing. ## Provenance boundary Existing runs remain untouched. Git initialization and lock updates are not retraining or renewed GPU acceptance evidence. Historical runs keep their original source/lock identities; restore their trusted recorded environment when needed rather than modifying provenance to force reuse.