disensor 0.9.2__tar.gz → 0.9.3__tar.gz

{disensor-0.9.2/src/disensor.egg-info → disensor-0.9.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: disensor
-Version: 0.9.2
+Version: 0.9.3
 Summary: Adversarial plan & code review with a declared residue. Emits, validates and CI-enforces residue declarations (residue/v0.4 schema).
 Author-email: Nicolas Rocchia <nicolasrocchia@gmail.com>
 License: MIT
@@ -146,7 +146,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: NicolasRocchia/disensor@v0.9.2
+      - uses: NicolasRocchia/disensor@v0.9.3
 ```
 
 The gate validates the declarations **the PR adds**, applies the policy and
@@ -288,6 +288,7 @@ to resolve:
 - **Organisation ruleset or required workflow**, defined outside the audited repository.
 - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys.
 - **Bootstrap**: the first PR that adds the config and the workflow cannot make itself the root of trust. Initial activation is an administrative step, prior to the gate meaning anything.
+- **When the pin goes up**: the workflow sits in the non-relaxable floor, so raising the pin through a PR costs an adversarial round for a change whose correctness a `git rev-parse` verifies better than any model. The convention in this repository is that a new pin **travels in the next PR of real work**, with its declaration, rather than in a PR of its own. **Exception**: if the release fixes gate security or changes the schema version, the pin goes up immediately, because the window in which the repository judges itself with the previous version stops being harmless: an old gate does not know the new contract and rejects what the freshly published CLI emits. This is a convention, not a control: as long as the branch does not require pull requests with bypass disabled for administrators too, nothing prevents pushing the pin directly ([#17](https://github.com/NicolasRocchia/disensor/issues/17)).
 
 Explicit limit: reading the policy from the base turns a one-step bypass into a
 two-step one, it does not eliminate it. Whoever can merge a relaxation uses it
@@ -467,7 +468,12 @@ it says.
 
 ## Status
 
-v0.9.2, on **residue/v0.4**. This version makes `disensor guide` hand over the
+v0.9.3, on **residue/v0.4**. This version writes down when the gate Action's own
+pin goes up: it travels in the next PR of real work, except when the release
+fixes gate security or changes the schema version, and it says out loud that
+this is a convention rather than a control
+([#17](https://github.com/NicolasRocchia/disensor/issues/17)). The previous
+version makes `disensor guide` hand over the
 event runbook as well as the artifact filling guide, so an agent that is not
 Claude Code gets from one command the same material the Claude Code skill
 carries, which is what the documentation had been promising since the round

{disensor-0.9.2 → disensor-0.9.3}/README.md

@@ -121,7 +121,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: NicolasRocchia/disensor@v0.9.2
+      - uses: NicolasRocchia/disensor@v0.9.3
 ```
 
 The gate validates the declarations **the PR adds**, applies the policy and
@@ -263,6 +263,7 @@ to resolve:
 - **Organisation ruleset or required workflow**, defined outside the audited repository.
 - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys.
 - **Bootstrap**: the first PR that adds the config and the workflow cannot make itself the root of trust. Initial activation is an administrative step, prior to the gate meaning anything.
+- **When the pin goes up**: the workflow sits in the non-relaxable floor, so raising the pin through a PR costs an adversarial round for a change whose correctness a `git rev-parse` verifies better than any model. The convention in this repository is that a new pin **travels in the next PR of real work**, with its declaration, rather than in a PR of its own. **Exception**: if the release fixes gate security or changes the schema version, the pin goes up immediately, because the window in which the repository judges itself with the previous version stops being harmless: an old gate does not know the new contract and rejects what the freshly published CLI emits. This is a convention, not a control: as long as the branch does not require pull requests with bypass disabled for administrators too, nothing prevents pushing the pin directly ([#17](https://github.com/NicolasRocchia/disensor/issues/17)).
 
 Explicit limit: reading the policy from the base turns a one-step bypass into a
 two-step one, it does not eliminate it. Whoever can merge a relaxation uses it
@@ -442,7 +443,12 @@ it says.
 
 ## Status
 
-v0.9.2, on **residue/v0.4**. This version makes `disensor guide` hand over the
+v0.9.3, on **residue/v0.4**. This version writes down when the gate Action's own
+pin goes up: it travels in the next PR of real work, except when the release
+fixes gate security or changes the schema version, and it says out loud that
+this is a convention rather than a control
+([#17](https://github.com/NicolasRocchia/disensor/issues/17)). The previous
+version makes `disensor guide` hand over the
 event runbook as well as the artifact filling guide, so an agent that is not
 Claude Code gets from one command the same material the Claude Code skill
 carries, which is what the documentation had been promising since the round

{disensor-0.9.2 → disensor-0.9.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "disensor"
-version = "0.9.2"
+version = "0.9.3"
 description = "Adversarial plan & code review with a declared residue. Emits, validates and CI-enforces residue declarations (residue/v0.4 schema)."
 readme = "README.md"
 requires-python = ">=3.10"

{disensor-0.9.2 → disensor-0.9.3}/src/disensor/__init__.py

@@ -1,2 +1,2 @@
 """disensor: residue declaration of adversarial review (controlled disagreement)."""
-__version__ = "0.9.2"
+__version__ = "0.9.3"

{disensor-0.9.2 → disensor-0.9.3/src/disensor.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: disensor
-Version: 0.9.2
+Version: 0.9.3
 Summary: Adversarial plan & code review with a declared residue. Emits, validates and CI-enforces residue declarations (residue/v0.4 schema).
 Author-email: Nicolas Rocchia <nicolasrocchia@gmail.com>
 License: MIT
@@ -146,7 +146,7 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: NicolasRocchia/disensor@v0.9.2
+      - uses: NicolasRocchia/disensor@v0.9.3
 ```
 
 The gate validates the declarations **the PR adds**, applies the policy and
@@ -288,6 +288,7 @@ to resolve:
 - **Organisation ruleset or required workflow**, defined outside the audited repository.
 - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys.
 - **Bootstrap**: the first PR that adds the config and the workflow cannot make itself the root of trust. Initial activation is an administrative step, prior to the gate meaning anything.
+- **When the pin goes up**: the workflow sits in the non-relaxable floor, so raising the pin through a PR costs an adversarial round for a change whose correctness a `git rev-parse` verifies better than any model. The convention in this repository is that a new pin **travels in the next PR of real work**, with its declaration, rather than in a PR of its own. **Exception**: if the release fixes gate security or changes the schema version, the pin goes up immediately, because the window in which the repository judges itself with the previous version stops being harmless: an old gate does not know the new contract and rejects what the freshly published CLI emits. This is a convention, not a control: as long as the branch does not require pull requests with bypass disabled for administrators too, nothing prevents pushing the pin directly ([#17](https://github.com/NicolasRocchia/disensor/issues/17)).
 
 Explicit limit: reading the policy from the base turns a one-step bypass into a
 two-step one, it does not eliminate it. Whoever can merge a relaxation uses it
@@ -467,7 +468,12 @@ it says.
 
 ## Status
 
-v0.9.2, on **residue/v0.4**. This version makes `disensor guide` hand over the
+v0.9.3, on **residue/v0.4**. This version writes down when the gate Action's own
+pin goes up: it travels in the next PR of real work, except when the release
+fixes gate security or changes the schema version, and it says out loud that
+this is a convention rather than a control
+([#17](https://github.com/NicolasRocchia/disensor/issues/17)). The previous
+version makes `disensor guide` hand over the
 event runbook as well as the artifact filling guide, so an agent that is not
 Claude Code gets from one command the same material the Claude Code skill
 carries, which is what the documentation had been promising since the round