bijux-canon-ingest
bijux-canon-ingest is the package that turns raw documents into deterministic
ingest artifacts and retrieval-ready structures. It is where cleaning,
chunking, package-local retrieval assembly, and ingest-facing boundaries live.
This package should help a maintainer answer practical questions such as:
- how does a source document become stable ingest output
- where do retrieval-oriented assembly steps belong
- which code is pure transformation logic and which code is adapter work
What This Package Takes And Produces
- takes: raw documents, ingest configuration, and package-local retrieval assembly inputs
- produces: cleaned records, chunks, retrieval-ready artifacts, and ingest boundary failures when source data breaks contract
- guarantees: deterministic transforms stay separable from adapters and the root import remains safe for dependency-light consumers
- does not do: own runtime replay policy, expose every internal helper as a stable promise, or define vector execution semantics for the rest of canon
Public API Routing
Use the package root for stable, dependency-light ingestion primitives. Reach into submodules only when you need a specific boundary:
bijux_canon_ingestfor stable transforms, result helpers, and shared ingest primitivesbijux_canon_ingest.applicationfor workflow orchestrationbijux_canon_ingest.interfacesfor CLI and HTTP edgesbijux_canon_ingest.configfor builder-style package configuration
Legacy continuity
- compatibility package:
bijux-rag - legacy import root:
bijux_rag - legacy command:
bijux-rag - canonical migration guide: Migration guidance
- retired repository target: https://github.com/bijux/bijux-rag (see Repository consolidation notes)
What this package owns
- document cleaning, normalization, and chunking
- ingest-local retrieval and indexing assembly
- package-local CLI and HTTP boundaries
- ingest-specific adapters, safeguards, and observability helpers
What this package does not own
- standalone vector execution semantics
- runtime-wide governance, persistence, or replay authority
- repository tooling and release automation
Source map
src/bijux_canon_ingest/processingfor deterministic document transformssrc/bijux_canon_ingest/retrievalfor retrieval-oriented models and assemblysrc/bijux_canon_ingest/applicationfor package workflowssrc/bijux_canon_ingest/infraandsrc/bijux_canon_ingest/integrationsfor adapterssrc/bijux_canon_ingest/interfacesfor CLI and HTTP edgestestsfor behavior, layout, and corpus-backed checks
Read this next
- Package guide
- Package overview
- Ownership boundary
- Architecture overview
- Operator workflows
- Compatibility packages
- Changelog
Primary entrypoint
- console script:
bijux-canon-ingest
Release Readiness
- release line prepared for publish:
0.3.9 - release date:
2026-07-04 - package changelog:
CHANGELOG.md
Metadata
Release files for bijux-canon-ingest 0.3.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bijux_canon_ingest-0.3.9.tar.gz | 104.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bijux_canon_ingest-0.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 293.1 kB
Release files / bijux_canon_ingest-0.3.9.tar.gz
| Download URL | bijux_canon_ingest-0.3.9.tar.gz |
|---|---|
| Size | 104.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57536435c8a6628dbe818c7d8d74b4b210757b9a6d593158d1bee538d40422f5
|
|
BLAKE2b-256 checksum How to use checksums |
7997edb0c04040c5e6b8cf180aea57fd7d1fe005940f1047d7f043d81019bb5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 4, 2026.
Transparency logRelease files / bijux_canon_ingest-0.3.9-py3-none-any.whl
| Download URL | bijux_canon_ingest-0.3.9-py3-none-any.whl |
|---|---|
| Size | 188.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
703ba5f052a74ee1f61e6bc7bfa668cef6f76f75359b2bb4c7122e33a3af0bf3
|
|
BLAKE2b-256 checksum How to use checksums |
a50907fbd0098bd06d8893bf184875cf7c75fbeccd6ee2397bbbf8255ea26fc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 4, 2026.
Transparency logSecurity for bijux-canon-ingest 0.3.9
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bijux_canon_ingest-0.3.9.tar.gz
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 Jul 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.