openDox-code
The code leg of the opendox project: the implementation and its
tests. The requirements it implements live in
opensoft/openDox-spec.
Clone the assembly root, not this repository. This leg is mounted as a
submodule at code/ inside
opensoft/openDox, which
is what pins the commit of this repository that the project currently is:
git clone --recurse-submodules https://github.com/opensoft/openDox.git
cd openDox
make bootstrap
Working here directly is fine — it is an ordinary repository with an ordinary
branch. What advancing this leg does NOT do is advance the project: that is a
commit in the assembly root moving the gitlink, contracts/code-pin.yaml and
any workflow @<sha> reference together.
Being the code leg confers no authority over the implementation. The split is navigation; authority travels in grants, and a project that keeps spec and code in one repository is reviewed identically.
Topic: xf-project-opendox.
Posture
Contributing guidelines and the code of conduct live in the assembly root,
not here: see
CONTRIBUTING.md
and
CODE_OF_CONDUCT.md
in opensoft/openDox. Security reports for this repository go through
SECURITY.md. The validate check is a required status check
on main, enforced by a repository ruleset — see
docs/branch-protection.md. It runs the whole
suite, tests/ and tests_runtime/, with the conftest chain in play and a
PostgreSQL service, and it declares no exclusion (plan 034 T036;
add-neutral-product-standalone-operability requirement 9). Until then it ran
a narrowed set of suites (RULED Q-L5 (b′), opensoft/openxFactory#656,
2026-09-10). That ruling gave the openDox → openXdox dependency as the reason,
but the dependency was inverted at import time first. The live cause of the
narrowing was the carved code's reaches into ideation_dashboard,
openxFactory's own package, and plan 034's phase 1 removed them.
Documentation
The doc index for this repository. Everything under docs/ is listed here,
and a new document is linked from this table in the same pull request that
adds it — the xFactory family's standing rule, levelled across all six
openDox/openXdox repositories by the OQ-O scaffold pass
(opensoft/openxFactory#656).
| document | what it is |
|---|---|
| docs/branch-protection.md | the repository ruleset that makes validate a required status check on main, its evaluate → active history, and the one policy difference between the two families |
| docs/profile-registration-runbook.md | the host profile: the one opendox.domain_profile.register() call a descendant makes at process start, what openDox reads off it, the default profile openDox's entry points register where no host has (and until when a host's registration still replaces it), how a process that builds nothing refuses, and how RULED ASK-4 Q5's one registration serves both legs' accessors without an import between them |
1 maintainer
Metadata
1 maintainer
Release files for opendox 0.1.0
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 | |
|---|---|---|---|---|
| opendox-0.1.0.tar.gz | 2.7 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opendox-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 MB
Release files / opendox-0.1.0.tar.gz
| Download URL | opendox-0.1.0.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56869b6208a8f7806410eab5626c2869641cb98064f98c6957a7825f2697efbf
|
|
BLAKE2b-256 checksum How to use checksums |
007341d0048f047215f1fb8fad3136ee2a64f01931b0f18508c85b57a318acc7
|
| 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 Oct 5, 2026.
Transparency logRelease files / opendox-0.1.0-py3-none-any.whl
| Download URL | opendox-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ecea00db6f9526d981fcf1bd595b1730243d448bca56bf2071ac21459e7b33c
|
|
BLAKE2b-256 checksum How to use checksums |
1575b5a9c45cb5be32a2d7d96c66503e164ca688148270aa308c22967241bc14
|
| 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 Oct 5, 2026.
Transparency logSecurity for opendox 0.1.0
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 opendox-0.1.0.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 Oct 5, 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.
