statute
statute is a command that will compile a constitution and the rules a
repository chooses into the instruction files coding agents read. It is
under development: so far it reads a rule set, statute.toml, and one
source of rules on disk, and writes the lock file, statute.lock,
AGENTS.md and, next to it, the skills and checks the rules need; what
it does is listed in
The command and the first version. On crates.io, 0.0.1 is
a placeholder that held the name and only prints a notice; the command
starts with 0.1.0. The project lives at
https://agent-constitution.luolc.com/, and its source at
https://github.com/Luolc/agent-constitution.
1 maintainer
Metadata
1 maintainer
Release files for statute 0.1.30
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| statute-0.1.30-py3-none-musllinux_1_2_x86_64.whl | Python 3 | none | Linux musl 1.2+ x86-64 | Details |
| statute-0.1.30-py3-none-musllinux_1_2_aarch64.whl | Python 3 | none | Linux musl 1.2+ ARM64 | Details |
| statute-0.1.30-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| statute-0.1.30-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| statute-0.1.30-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| statute-0.1.30-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 15.3 MB
Release files / statute-0.1.30-py3-none-musllinux_1_2_x86_64.whl
| Download URL | statute-0.1.30-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
daaeac95a8137048f3b353e7bf7dd1f6ae10fc5890f095024403d73f2a5c974a
|
|
BLAKE2b-256 checksum How to use checksums |
d63e76c020d517104aab33a48552e22e8309110f399f5f061f28010404f64ad0
|
| 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 20, 2026.
Transparency logRelease files / statute-0.1.30-py3-none-musllinux_1_2_aarch64.whl
| Download URL | statute-0.1.30-py3-none-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
d22881d9cd7a893092d89a01de0eb7f3df08fca885983e27f33e43339b585c9b
|
|
BLAKE2b-256 checksum How to use checksums |
7436bf5935308f1d96a82bbae7876b8da0094e21562085214b344f1d80d51f18
|
| 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 20, 2026.
Transparency logRelease files / statute-0.1.30-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | statute-0.1.30-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
15db525340f46203dcf6f6674ed9f6e22bb0e8cab573df8c5f4191ba7c6feb66
|
|
BLAKE2b-256 checksum How to use checksums |
0c92959a086438c490c255e6599147b3bcb9547c100459f5f2b04f52f78f3d97
|
| 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 20, 2026.
Transparency logRelease files / statute-0.1.30-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | statute-0.1.30-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
70b29ba33a13c417e6fbca684d1ef9ca485276a251dd57ddaef1f84c72da2380
|
|
BLAKE2b-256 checksum How to use checksums |
dbde771774223e1aa4abeef4ba551442803e6a1fb87c3e94ebbd875f40d75525
|
| 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 20, 2026.
Transparency logRelease files / statute-0.1.30-py3-none-macosx_11_0_arm64.whl
| Download URL | statute-0.1.30-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2b6fb4fbeecbcaaf335a516b70a23beee55add4b1f1c38bce6cd8c4d72da4ecb
|
|
BLAKE2b-256 checksum How to use checksums |
6d2ee6ba3a7d47432f65704e1311ae68c098dcfdb25080f32d3111f2286f1847
|
| 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 20, 2026.
Transparency logRelease files / statute-0.1.30-py3-none-macosx_10_12_x86_64.whl
| Download URL | statute-0.1.30-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
faaf6a33e4ba783676abf7da1db4c9ddb370c90af4e6c84817fafb27479fef96
|
|
BLAKE2b-256 checksum How to use checksums |
372d57fda5c17e699831f645175a2bdfc1f877d47985970720db9c49f0998f0e
|
| 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 20, 2026.
Transparency logSecurity for statute 0.1.30
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 6 files in this release have been uploaded with provenance metadata.
Attestation for statute-0.1.30-py3-none-musllinux_1_2_x86_64.whl
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 20, 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.
