Publish AUREOLE-R to your Hugging Face
This package contains the complete research release. The public destination is PureOne/AUREOLE-R-v3. Your write token belongs in the private prompt on your computer; the ZIP contains no token.
Windows: three steps
- Right-click the ZIP and select Extract All. Open its
AUREOLE_R_v3.0.0_HuggingFacefolder. - Double-click PUBLISH_TO_HUGGINGFACE.bat. Python 3.10 or later and internet access are required. The launcher creates its own publication environment and installs the pinned Hugging Face client.
- Paste your Hugging Face write token when prompted and press Enter. Input is hidden: no characters or asterisks appear. Wait for PUBLICATION VERIFIED.
The script prints the public page and immutable commit URL. publication_receipt.json records both and the verification evidence. It contains no token and is excluded from future uploads. The launcher does not save a login credential or place your token in command arguments. A token can also be provided through the existing HF_TOKEN environment variable.
The uploader targets a public model repository because this all-in-one research release includes a trained visibility prior with its paper, code and evidence. It does not create an inference endpoint or paid compute job. It does not submit an arXiv paper or claim an HF Paper Page without an arXiv identifier.
Other platforms or a different personal account
python -m pip install -r requirements-publish.txt
python scripts/publish_hf.py
python scripts/publish_hf.py --publish
The first script invocation is an offline checksum check. To choose another repository, use --repo YOUR_ACCOUNT/AUREOLE-R-v3. On Windows you can run PUBLISH_TO_HUGGINGFACE.bat --repo YOUR_ACCOUNT/AUREOLE-R-v3 from a terminal. The uploader checks that the token owner matches the personal account namespace; organization publishing is outside this launcher's scope. Citation metadata records the default intended destination, so cite the actual immutable URL from your receipt if you use another destination.
What the uploader verifies
Only reviewed files listed in CHECKSUMS.sha256 are staged. Files added after extraction, virtual environments, local credentials and generated receipts are excluded. The staging copy is checked again before authentication. The script refuses private/gated repositories, unrelated remote files or differing bytes. An empty destination or a partially uploaded, byte-matching copy can resume. It never deletes remote files or changes an existing repository's visibility. A parent-commit condition protects against concurrent edits.
After upload, a client without credentials reads the immutable commit and checks every release file's size and Git-blob or LFS digest. It also downloads and checks the public SHA-256 manifest. Success is reported only after those checks. The checksums protect integrity of the distributed bytes; they are not a digital signature or peer-review certificate.
If something interrupts the upload
| Message / situation | Action |
|---|---|
| Python missing | Install Python 3.10+ from python.org and reopen the launcher. |
| Checksum mismatch | Extract a fresh copy. Do not edit files before publishing this verified edition. |
| Wrong account | Use the token for PureOne, or set --repo to your own personal namespace. |
| HTTP 401 / 403 | Check token validity and permission to create/write this destination. A fine-grained token must authorize the relevant resource and action. |
| Different remote content | Use a new repository name with --repo. The launcher does not overwrite another release. |
| Connection or public-verification failure | Rerun the same package. Matching committed content is recognized; no deletion or duplicate project is needed. |
| No visible token characters | Expected: paste once, then press Enter. |
Do not run from inside the ZIP preview. Keep the extracted folder structure intact. If your terminal cannot hide token entry, the uploader stops instead of echoing it.
Research entry points
52-page paper 路 Expert review 路 Reproduction 路 AI-agent guide
The scientific reference is verified within its finite CPU scope. General real-time unified SR/RR/FG and GPU performance remain unvalidated. The publication edition preserves all scientific source, weights, protocols and evidence.
Publication implementation references
The launcher uses the official Hub API for explicit commit guards and verification. The card follows Hub model-card metadata. Token permissions are described in Hugging Face access-token documentation. These implementation references were checked on 19 September 2026. The installed SDK contract is pinned to huggingface-hub==1.32.0.