pgc_install
Protocol-Governed Computing — the whole toolchain in one install.
This repository publishes the pgc distribution. It is the composition as installable
software, the counterpart to pgc_release, which is the same composition as sealed
evidence — assembled, immutable, and cited by DOI. The parallel is in role, not in citation:
a release is a thing a paper points at; an install is a thing that changes each version.
pip install pgc
That brings in the seven packages of the family, pinned to one composition.
Two steps, not one
Installing the toolchain is half of a working environment. The compiler resolves the
governance surface from PGC_PLATFORM_ROOT — fail-hard, cwd-independent, zero
inference — so the declarations come from a repository you point at, not from a
wheel. A registry inside a package would be a second governance surface competing
with the repository's, and a build could then be governed by a stale copy.
git clone https://github.com/protocol-governed-computing/software_governance
export PGC_PLATFORM_ROOT=$PWD/software_governance
pgc # reports what is installed and whether the anchor resolves
The family
| Package | Role |
|---|---|
pgc-compiler |
declarations → compiled projections |
pgc-assembler |
projections → sealed snapshot |
pgc-runtime |
snapshot → governed execution |
pgc-inspector |
snapshot → read-only inspection |
pgc-transformation |
change request → protocol artifacts |
pgc-governance |
the governance surface and its capability implementations |
pgc-workloads |
the workloads that make conformance observable |
pgc-domains |
the business domain implementations the composed snapshot binds |
Versioning. Two schemes. Each repository's VERSION is a monotonic composition ordinal —
internal build accounting, tagged release-<N>, never published. PUBLIC_VERSION is the platform's
public identity, tagged on every component repository; the platform is at v2.
The published version is the public one: v2 is 2.0.0. The family releases in lockstep, so pgc
pins exact versions rather than ranges. The standard these packages implement is a separate artifact on
its own track and is not this number.
The standard these packages implement is published separately: https://doi.org/10.5281/zenodo.22150616
1 maintainer
Metadata
1 maintainer
Release files for protocol-governed-computing 2.0.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 | |
|---|---|---|---|---|
| protocol_governed_computing-2.0.0.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| protocol_governed_computing-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / protocol_governed_computing-2.0.0.tar.gz
| Download URL | protocol_governed_computing-2.0.0.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93d5183e818ef77e6caf42b6ab25bc5912549aa13c923f3120835bac95b14b36
|
|
BLAKE2b-256 checksum How to use checksums |
5f267eb74812e8c8841cde6e5827a72a8303a22e7c10bf9b37aa4eebc39c9dd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / protocol_governed_computing-2.0.0-py3-none-any.whl
| Download URL | protocol_governed_computing-2.0.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c8b0b7ecde539742fbcf474b3b88bb1675e76b92e0465d73e5fc8b54056a6fed
|
|
BLAKE2b-256 checksum How to use checksums |
2034c9019d92be747a4282f3f430666049a2fa81b8d0604388506fe2ad5d2572
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for protocol-governed-computing 2.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
