Spaces:
Running on Zero
Running on Zero
File size: 3,155 Bytes
8947dc2 f8768df 9b4dbef f8768df 9b4dbef c4aee46 8947dc2 f8768df 9b4dbef f8768df c4aee46 f8768df 9b4dbef f8768df 9b4dbef f8768df 8947dc2 f8768df 9b4dbef f8768df | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 | # RANGE 0.1.0a3 release-candidate contract
This directory is the authoritative source for the **RANGE** research alpha.
## Identity
- Product: `RANGE`
- Distribution: `range-curate`
- Import namespace: `range_curate`
- Version: `0.1.0a3`
- Supported runtime: CPython 3.10
- Supported backend: CPU
- License: MIT
- Publication state: not published
The distribution name is descriptive while the product name remains RANGE.
## Required artifacts
A candidate build must produce:
- a Linux wheel and a Windows wheel;
- one source distribution;
- bundled taxonomy YAML;
- bundled frozen Unicode tables;
- the native extension;
- `LICENSE`, `README.md`, `CHANGELOG.md`, and `CITATION.cff`; and
- the `app/` Space scaffold, Docker build, offline exporter, and validator in the
source distribution.
## Required validation
CI is deliberately small and manually invoked. The `range-curate-release-candidate`
workflow has only two jobs:
1. **Linux package + Space smoke** validates source syntax, the Space scaffold, the
Rust dependency lock, wheel/sdist metadata and contents, clean installations,
public contracts, README output, the exported Docker context, the running Gradio
service, and the named `/analyze` and `/batch` endpoints.
2. **Windows package smoke** validates the native Windows artifact, source distribution,
metadata and contents, clean installations, public contracts, PyArrow support, and
README output.
The broader parent research project and historical acceleration suites are not package-release
gates. They remain available through the separate manual/main-only `repository-tests`
workflow.
## Why the workflow is manual
While RANGE remains inside a larger private monorepo, every feature-branch push can
otherwise produce duplicate `push` and `pull_request` runs. Manual invocation keeps the
PR readable and conserves hosted-runner minutes while preserving the checks that matter
before publication or final technical sign-off.
## Explicit no-publish boundary
The repository contains no PyPI token, trusted-publisher deployment job, release tag,
Space creation step, or upload command for this package. CI artifacts are uploaded only
to the associated GitHub Actions run for inspection. The Space exporter writes only to
a local directory.
Publishing requires a separate, explicit human decision after:
- ownership and license review;
- inspection of both platform artifacts;
- confirmation of the final repository and documentation URLs;
- review of the public Space privacy notice and input limits;
- a clean release commit;
- a version and tag decision; and
- intentional package-index and/or Space deployment workflows added in a later change.
## Alpha support boundary
`0.1.0a3` makes a narrow claim:
> An exact, CPU-first, research-alpha package for traceable financial-news relevance
> screening against a versioned general-economy taxonomy.
It does not claim complete semantic recall, investment usefulness, universal
throughput, Python-version portability beyond 3.10, or paper-grade performance
generalization.
|