pgc-compiler 2.0.0__tar.gz → 4.0.0__tar.gz

{pgc_compiler-2.0.0/pgc_compiler.egg-info → pgc_compiler-4.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pgc-compiler
-Version: 2.0.0
+Version: 4.0.0
 Summary: PGC protocol compiler — compiles governed declarations into sealed, verified projections (import package: compiler)
 Author-email: Bhash Ganti <bachipeachy@gmail.com>
 License-Expression: Apache-2.0
@@ -173,7 +173,7 @@ Apache-2.0. See `LICENSE` and `NOTICE`.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -186,8 +186,18 @@ export PGC_PLATFORM_ROOT=$PWD/software_governance
 pgc            # reports what is installed and whether the anchor resolves
 ```
 
-`PGC_BUILD_ROOT` (compiled output, keeping the governance repo read-only) and `PGC_DOMAIN_ROOTS`
-(additional domains contributing their own `registry/structures`) are optional.
+`PGC_DOMAIN_ROOTS` names an additional domain contributing its own `registry/structures` — the
+directory that *directly contains* it, not the repository above it; pointing one level too high is a
+silent no-op. `PGC_SNAPSHOT_ROOT` is where compiled output is written, and each domain build needs
+its own: every layer's output consolidates into one root, and verification rejects any file in that
+root the current build did not declare. `PGC_SNAPSHOT_PROFILES` is the directory holding snapshot
+profiles, required by the assembler and the runtime alike.
+
+`PGC_BUILD_ROOT` is accepted and reported and **nothing reads it** — `PGC_SNAPSHOT_ROOT` is the
+anchor that controls output.
+
+The full sequence, with the repositories it needs, is in
+[`pgc_install`](https://github.com/protocol-governed-computing/pgc_install).
 
 **Versioning.** Two schemes, and the published version follows the second.
 
@@ -195,9 +205,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v4` is `4.0.0`.** The standard the 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

{pgc_compiler-2.0.0 → pgc_compiler-4.0.0}/README.md

@@ -145,7 +145,7 @@ Apache-2.0. See `LICENSE` and `NOTICE`.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -158,8 +158,18 @@ export PGC_PLATFORM_ROOT=$PWD/software_governance
 pgc            # reports what is installed and whether the anchor resolves
 ```
 
-`PGC_BUILD_ROOT` (compiled output, keeping the governance repo read-only) and `PGC_DOMAIN_ROOTS`
-(additional domains contributing their own `registry/structures`) are optional.
+`PGC_DOMAIN_ROOTS` names an additional domain contributing its own `registry/structures` — the
+directory that *directly contains* it, not the repository above it; pointing one level too high is a
+silent no-op. `PGC_SNAPSHOT_ROOT` is where compiled output is written, and each domain build needs
+its own: every layer's output consolidates into one root, and verification rejects any file in that
+root the current build did not declare. `PGC_SNAPSHOT_PROFILES` is the directory holding snapshot
+profiles, required by the assembler and the runtime alike.
+
+`PGC_BUILD_ROOT` is accepted and reported and **nothing reads it** — `PGC_SNAPSHOT_ROOT` is the
+anchor that controls output.
+
+The full sequence, with the repositories it needs, is in
+[`pgc_install`](https://github.com/protocol-governed-computing/pgc_install).
 
 **Versioning.** Two schemes, and the published version follows the second.
 
@@ -167,9 +177,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v4` is `4.0.0`.** The standard the 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

pgc_compiler-4.0.0/VERSION

@@ -0,0 +1 @@
+16

pgc_compiler-4.0.0/compiler/VERSION

@@ -0,0 +1 @@
+16

{pgc_compiler-2.0.0 → pgc_compiler-4.0.0/pgc_compiler.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pgc-compiler
-Version: 2.0.0
+Version: 4.0.0
 Summary: PGC protocol compiler — compiles governed declarations into sealed, verified projections (import package: compiler)
 Author-email: Bhash Ganti <bachipeachy@gmail.com>
 License-Expression: Apache-2.0
@@ -173,7 +173,7 @@ Apache-2.0. See `LICENSE` and `NOTICE`.
 | `pgc-workloads` | `conformance_workloads` | the workloads that make conformance observable |
 | `pgc-domains` | `business_domains` | the business domain implementations the composed snapshot binds |
 
-`pip install pgc` brings in the whole family.
+`pip install protocol-governed-computing` brings in the whole family.
 
 **Installing the toolchain is one of two steps.** The compiler resolves the governance surface from
 `PGC_PLATFORM_ROOT` — fail-hard, cwd-independent, zero inference — so the *declarations* come from a
@@ -186,8 +186,18 @@ export PGC_PLATFORM_ROOT=$PWD/software_governance
 pgc            # reports what is installed and whether the anchor resolves
 ```
 
-`PGC_BUILD_ROOT` (compiled output, keeping the governance repo read-only) and `PGC_DOMAIN_ROOTS`
-(additional domains contributing their own `registry/structures`) are optional.
+`PGC_DOMAIN_ROOTS` names an additional domain contributing its own `registry/structures` — the
+directory that *directly contains* it, not the repository above it; pointing one level too high is a
+silent no-op. `PGC_SNAPSHOT_ROOT` is where compiled output is written, and each domain build needs
+its own: every layer's output consolidates into one root, and verification rejects any file in that
+root the current build did not declare. `PGC_SNAPSHOT_PROFILES` is the directory holding snapshot
+profiles, required by the assembler and the runtime alike.
+
+`PGC_BUILD_ROOT` is accepted and reported and **nothing reads it** — `PGC_SNAPSHOT_ROOT` is the
+anchor that controls output.
+
+The full sequence, with the repositories it needs, is in
+[`pgc_install`](https://github.com/protocol-governed-computing/pgc_install).
 
 **Versioning.** Two schemes, and the published version follows the second.
 
@@ -195,9 +205,9 @@ pgc            # reports what is installed and whether the anchor resolves
   composition rather than each repo: they release together and the governance closure forces lockstep,
   so the ordinal names which composition a repo belongs to. Development happens on `dev/<N>` and each
   cycle is tagged `release-<N>`. This is not published.
-- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v2`**.
+- **Public** — `PUBLIC_VERSION`, tagged on every component repository. The platform is at **`v3`**.
 
-**The published version is the public one: `v2` is `2.0.0`.** The standard the packages implement is a
+**The published version is the public one: `v4` is `4.0.0`.** The standard the 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

{pgc_compiler-2.0.0 → pgc_compiler-4.0.0}/pyproject.toml

@@ -5,7 +5,7 @@ backend-path = ["."]
 
 [project]
 name = "pgc-compiler"
-version = "2.0.0"
+version = "4.0.0"
 description = "PGC protocol compiler — compiles governed declarations into sealed, verified projections (import package: compiler)"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -55,5 +55,8 @@ include = ["compiler*"]
 
 [tool.setuptools.package-data]
 # VERSION has no extension, so it needs naming explicitly — it carries the
-# composition ordinal an installed wheel cannot otherwise reach.
-"*" = ["*.md", "*.yaml", "*.json", "*.sh", "VERSION"]
+# composition ordinal an installed wheel cannot otherwise reach. Scoped to the
+# package rather than "*": a bare pattern applies to every found package and ships
+# whatever later sits beside a module. That is how declarations reached two other
+# wheels in this family.
+"compiler" = ["VERSION"]

pgc_compiler-2.0.0/VERSION

@@ -1 +0,0 @@
-14

pgc_compiler-2.0.0/compiler/VERSION

@@ -1 +0,0 @@
-14