dougvk/Unlimited-OCR-RDNA4

1# Publishing checklist2 3The repository intentionally separates source publication from package/model publication.4 5## Hugging Face6 71. Review `git diff --check`, tests, build artifacts, and validation evidence.82. Create `dougvk/Unlimited-OCR-RDNA4` as a private model repository.93. Push the reviewed initial commit.104. Verify the model card, source tree, package artifacts, and remote hashes.115. Make the repository public only after those checks pass.126. Tag `v0.1.0` only after the clean-environment gate in `docs/VALIDATION.md` is reproduced.13 14## PyPI (deferred)15 16Do not publish `v0.1.0` to PyPI. The supported installation contract is the repository's hash-locked bootstrap, while an17installed wheel cannot yet reproduce that bootstrap without returning to the source checkout. Building and running18`twine check` remains a packaging gate, not authorization to upload. A later PyPI release should bundle an equivalent19bootstrap entry point and independently verify a fresh wheel installation first.20 21Do not upload or duplicate Baidu's checkpoint. The repository contains the runtime source and packages and links to the22original `baidu/Unlimited-OCR` weights.23 24The repository should be classified as documentation for a runtime/integration, not as a runnable Transformers25pipeline, new model, checkpoint, fine-tune, or kernel port.26 27## GitHub (optional mirror)28 29If a GitHub mirror is created later, update the project URLs consistently and enable private vulnerability reporting.30 31## Upstream32 33After publication:34 351. open a concise Baidu discussion or documentation pull request with the verified configuration and evidence;362. offer the gfx1201 bootstrap and validation findings to `AIwork4me/Unlimited-OCR-ROCm`;373. avoid claiming universal ROCm or all-RDNA support until independently reproduced.38