bijux-canon-reason
bijux-canon-reason is the package that turns available evidence into planned
reasoning steps, structured claims, and verification outcomes. It is where
reasoning behavior is made explicit enough to inspect, test, and defend.
If you need to understand how claims are formed, how reasoning steps are planned and executed, how evidence is used, or where verification lives, start here. If you need runtime governance, storage, or vector execution internals, you are outside this package's boundary.
What This Package Takes And Produces
- takes: evidence bundles, reasoning plans, verification gates, and package-local tool inputs
- produces: structured claims, reasoning step outputs, verification outcomes, and inspectable reasoning artifacts
- guarantees: reasoning behavior stays explicit enough to test and challenge, with verification attached to the reasoning surface itself
- does not do: persist runtime-wide state, own replay authority, or replace ingest and retrieval package boundaries
Legacy continuity
- compatibility package:
bijux-rar - legacy import root:
bijux_rar - legacy command:
bijux-rar - canonical migration guide: Migration guidance
- retired repository target: https://github.com/bijux/bijux-rar (see Repository consolidation notes)
What this package owns
- reasoning plans, claims, and evidence-aware reasoning models
- execution of reasoning steps and local tool dispatch
- verification and provenance checks that belong to reasoning itself
- package-local CLI and API boundaries
What this package does not own
- runtime persistence, replay authority, or execution governance
- ingest and index engines
- repository tooling and release automation
Source map
src/bijux_canon_reason/planningfor planning behaviorsrc/bijux_canon_reason/reasoningfor claim and reasoning semanticssrc/bijux_canon_reason/executionfor step executionsrc/bijux_canon_reason/verificationfor checks and outcomessrc/bijux_canon_reason/interfacesandsrc/bijux_canon_reason/apifor boundariestestsfor executable protection of the package contract
Read this next
- Package guide
- Ownership boundary
- Architecture overview
- Interface contracts
- Compatibility packages
- Test strategy
- Changelog
Primary entrypoint
- console script:
bijux-canon-reason
Release Readiness
- release line prepared for publish:
0.3.9 - release date:
2026-07-04 - package changelog:
CHANGELOG.md
1 maintainer
Metadata
1 maintainer
Release files for bijux-canon-reason 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_reason-0.3.9.tar.gz | 57.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bijux_canon_reason-0.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 155.5 kB
Release files / bijux_canon_reason-0.3.9.tar.gz
| Download URL | bijux_canon_reason-0.3.9.tar.gz |
|---|---|
| Size | 57.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62bd42127da2a69a219be1dcfd7ec4a4db036816859cb5650e075cb68fc745db
|
|
BLAKE2b-256 checksum How to use checksums |
3a0423d66be0a2fecc1ded909dbafdb1ac31756548ae35799fb0bc9cb964468c
|
| 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_reason-0.3.9-py3-none-any.whl
| Download URL | bijux_canon_reason-0.3.9-py3-none-any.whl |
|---|---|
| Size | 98.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
557808a0137ae7e5676f8fb75f49f72ab742c3d3bee2bf2b7580bb448bb6f25c
|
|
BLAKE2b-256 checksum How to use checksums |
b68fbce800b8bbd3d896e36a8c1a7b792b537d7c2e1fa68e37b4d075839011cc
|
| 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-reason 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_reason-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.
