This release is a pre-release and may not be stable for production use.
ProDocuX Kernel
Deterministic document kernel for ProDocuX. Runtime does not call any LLM API (semantic drafting stays on the solver side).
License: Apache-2.0. See LICENSE.
Current prerelease on PyPI: 0.3.0rc5, published from tag
v0.3.0rc5 at commit e09684059519c16c8ec517e8f988e440ad3c9d09.
The next unpublished candidate is 0.3.0rc7. Public tag
v0.3.0rc6 did not pass the release workflow and is retained only as an
audit record; it is not a PyPI release or consumer pin.
This Kernel-only release fixes deterministic PDF wrapping, explicit line breaks, pagination, and mixed Latin/CJK font selection without changing frozen contracts. See rc5 publication record.
python -m pip install "prodocux==0.3.0rc5"
Documents
ARCHITECTURE.md— public architecture overviewCONTRACT.md— boundaries, API, scoring contractdocs/PHASE0_DECISIONS.md— Phase 0 sidecar, sink, and private-auth paper freezeCAPABILITY_REQUESTS.md— capability request templatedocs/RELEASE.md— release-candidate boundary and checksdocs/RELEASE_RC5.md— Kernel rc5 scope, gates, and publication boundarydocs/RELEASE_RC7.md— unpublished P0b template-conformance release candidatecompatibility/pdx_prodocux_compatibility_v3.json— frozen additive render/extract pins and G1A render-conformance fixture digestscompatibility/pdx_prodocux_release_v1.json— published rc2/a2 tags, package versions, release assets, and publication statuscompatibility/pdx_prodocux_release_rc3_a3.json— published rc3/a3 tags, package hashes, and workflow evidence; does not rewrite v1compatibility/pdx_prodocux_release_rc4_a4.json— current rc4/a4 release pins, hashes, publication evidence and security boundarycompatibility/pdx_prodocux_release_rc5.json— Kernel-only rc5 source pin, hashes, workflow evidence, and downstream boundarycompatibility/pdx_prodocux_compatibility_v2.json— 0.3.0rc1 prerelease versions, operations, and schema digestscompatibility/pdx_prodocux_compatibility_v1.json— frozen historical compatibility evidence
Install
git clone https://github.com/prodocux/prodocux.git
cd prodocux
.\runtime\install.ps1 -Fresh
.\runtime\verify.ps1
Or:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\.venv\Scripts\python.exe -m pytest -q
Install the deterministic extract/render prerelease from PyPI:
python -m pip install "prodocux==0.3.0rc2"
See the
prodocux PyPI 0.3.0rc2 release
and
GitHub prerelease.
The older published wheel
prodocux PyPI 0.3.0rc1
predates the additive extract/render freeze and must not be overwritten. Frozen
compatibility v3 still pins implementation commit
53c4784d4b2bae4437252a287193e897973e8474. See
docs/RELEASE.md.
See runtime/INSTALL.md for environment variables and
private-sidecar notes.
Release maintainers can verify a wheel from an isolated temporary directory:
python scripts/verify_clean_install.py
See docs/RELEASE.md for the PyPI Trusted Publisher and
GitHub approval-boundary workflow.
Test
.\.venv\Scripts\python.exe -m pytest -q
Start API
.\.venv\Scripts\python.exe run_kernel.py # http://localhost:8900/v1
Available capabilities
| Component | Endpoint | Status |
|---|---|---|
| Structure invariants (L0) | POST /v1/validate-structure |
shipped |
| Scorer (L0–L3) | POST /v1/score |
shipped |
| Review capture | POST /v1/review/start, /commit |
shipped |
| Version | GET /v1/version |
shipped |
| Legacy semantic extract/learn and path-shaped render | POST /v1/extract, /learn, /render |
stub or 501 |
| Deterministic block extraction | POST /v1/intake/extract-blocks |
shipped |
| Deterministic artifact render | POST /v1/render/artifact |
shipped |
| Render capabilities/artifact retrieval | GET /v1/render/capabilities, /artifacts/{artifact_id} |
shipped |
| Deterministic PDF page intake | POST /v1/intake/extract-pages |
shipped |
| JPEG/PNG technical profile | POST /v1/intake/profile-image |
shipped |
| Typed evidence verification | POST /v1/verify/evidence-bundle |
shipped |
| Normalized structured diff | POST /v1/compare/normalized-profiles |
shipped |
The PDF intake endpoint accepts only a bounded base64 payload and a plain
.pdf basename. It returns source SHA-256, bounded page text, truncation
disclosure, and an explicit ocr_required status without persisting the
source document or calling an LLM.
GET /v1/intake/capabilities is the authoritative machine-readable source
for available intake operations and their raw-byte/page ceilings. Clients
should discover these limits instead of copying constants into adapters.
The evidence verifier accepts already-extracted typed evidence and declarative
presence, equality, numeric-range, and date/version checks. It returns stable
pass/fail/review reasons without interpreting product claims or regulations.
Image OCR is available only through an explicitly injected bounded backend;
otherwise the profile reports ocr_unavailable. Normalized diff reports
source-linked structural/value changes but leaves business impact to the host.
Library hosts may inject an opaque artifact:// resolver. ProDocuX rejects
network/local-path identities at this boundary and verifies declared media
type, size, and SHA-256 before returning bytes; storage authorization and
tenant isolation remain host responsibilities.
Flagship pipeline
Deterministic template extract → field mapping → precise write → structure repair → L0 gate.
Content drafts are supplied by the solver as drafts.json.
See examples/pif_tw/ for curated synthetic fixtures (no customer documents).
Skills (first-party)
| Skill | Module |
|---|---|
| Structure health | skills.structure_health |
| Number audit | skills.number_audit |
| Version diff | skills.version_diff |
| Clause diff | skills.clause_diff |
| Doc assemble | skills.doc_assemble |
| PIF audit (TW) | skills.pif_audit |
| PDF extract | skills.pdf_extract |
All first-party skills are deterministic. CLI messages support en and zh-TW.
Acknowledgments
Codex and Cursor contributed implementation support, contract hardening, and cross-review for the multi-format intake upgrade. Final design and release decisions remain with the project maintainers.
Release files for prodocux 0.3.0rc7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| prodocux-0.3.0rc7.tar.gz | 161.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| prodocux-0.3.0rc7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 321.7 kB
Release files / prodocux-0.3.0rc7.tar.gz
| Download URL | prodocux-0.3.0rc7.tar.gz |
|---|---|
| Size | 161.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
391b3c20ea1bdfd125f9edb923fe7b4fbb29c25573949c416ae825dcfb0dea5b
|
|
BLAKE2b-256 checksum How to use checksums |
ca0b06ba9efa7e5ee101afc0c6621633568261b76301e809d9a7c48b75ca8c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / prodocux-0.3.0rc7-py3-none-any.whl
| Download URL | prodocux-0.3.0rc7-py3-none-any.whl |
|---|---|
| Size | 160.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9dd26f4f7fa8db489a54c2a6f8ae053b11094d1945d817613f2763d3b641c48d
|
|
BLAKE2b-256 checksum How to use checksums |
8f27afcd3366efbaba15fdd51849c91c104fd3742a0ba2e38ed02f6e3bb38468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log