Spaces:
Running on Zero
Running on Zero
| # RANGE 0.1.0a3 technical sign-off | |
| This document defines the bounded technical sign-off for the unpublished research | |
| alpha. It does not authorize publication, tagging, release creation, Space deployment, | |
| or merge. | |
| ## Identity | |
| - Product: **RANGE** | |
| - Distribution: `range-curate` | |
| - Python namespace: `range_curate` | |
| - Native Rust crate: `range_curate_native` | |
| - Version: `0.1.0a3` | |
| - Runtime: CPython 3.10 | |
| - Shipping backend: exact CPU/Rust | |
| Shipping source, wheels, and source distributions must not contain retired package | |
| identifiers. The repository URL may retain the parent repository's historical name; | |
| that is not a package identity. | |
| ## Required current-head evidence | |
| Technical sign-off intentionally has only two required jobs. Manually run the | |
| `range-curate-release-candidate` workflow on the exact commit being reviewed and require: | |
| 1. **Linux package + Space smoke** — source validation, Rust lock/format checks, wheel | |
| and source-distribution construction, metadata and archive inspection, clean | |
| installs, public package contracts, README output verification, deterministic Space | |
| export, Docker build, Gradio health check, and `/analyze` and `/batch` endpoint | |
| discovery. | |
| 2. **Windows package smoke** — native Windows wheel and source-distribution build, | |
| metadata/archive inspection, clean installs, package contracts, PyArrow coverage, | |
| and README output verification. | |
| The full parent research project deterministic suite and historical acceleration suite are not | |
| RANGE package sign-off gates. They remain available in `repository-tests` for a | |
| manual run and execute after integration to `main`. | |
| A success recorded for an older commit is not sufficient. | |
| ## Taxonomy non-change boundary | |
| README, app, CI, and package-identity work must not change the bundled taxonomy | |
| configuration, entity catalog, lexical catalog, effective dates, exposure mappings, | |
| matching rules, or decision behavior. Package presentation and taxonomy design are | |
| separate contracts. | |
| ## No-publish boundary | |
| Passing the manual gate leaves the pull request open and unmerged. It creates no PyPI | |
| or TestPyPI upload, trusted-publisher relationship, registry credential, Git tag, | |
| GitHub release, Hugging Face Space, deployment, or automatic merge. Publication | |
| requires a separate explicit change and human decision. | |