pawl-gate 0.1.0__tar.gz

pawl_gate-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

pawl_gate-0.1.0/PKG-INFO

@@ -0,0 +1,182 @@
+Metadata-Version: 2.4
+Name: pawl-gate
+Version: 0.1.0
+Summary: Ratchet gate for automated coding work. Code can only move forward.
+Author: Zero-State LLC
+License-Expression: Apache-2.0
+Project-URL: Source, https://github.com/Zero-State-LLC/pawl
+Project-URL: Issues, https://github.com/Zero-State-LLC/pawl/issues
+Keywords: ratchet,ci,testing,ai-agents,reward-hacking,quality-gate
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Requires-Dist: mypy>=1.11; extra == "dev"
+Dynamic: license-file
+
+# Pawl
+
+**Code can only move forward.**
+
+[![CI](https://github.com/Zero-State-LLC/pawl/actions/workflows/ci.yml/badge.svg)](https://github.com/Zero-State-LLC/pawl/actions/workflows/ci.yml)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue)](pyproject.toml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+[![Dependencies: none](https://img.shields.io/badge/dependencies-none-brightgreen)](pyproject.toml)
+
+Pawl is a ratchet gate for automated coding work. A change passes only if no
+test that passed now fails, no test disappeared or got skipped, and nobody
+loosened the gate itself. Known failures are allowed and can only go down.
+
+## The problem
+
+Coding agents told to "make the tests pass" sometimes change the tests instead
+of the code. Researchers have measured it: agents modify tests, overload `==`,
+and special-case inputs when a task is hard
+([ImpossibleBench](https://arxiv.org/abs/2510.20270),
+[EvilGenie](https://arxiv.org/abs/2511.21654),
+[METR](https://metr.org/blog/2025-06-05-recent-reward-hacking/)). Asking them
+not to is unreliable. A plain "tests must pass" check cannot help when the
+suite already has known failures, and a count-based ratchet misses a fixed test
+that hides a new failure, a skipped test, or a rewritten assertion.
+
+Here an agent "fixes" `add` and edits a test so the suite stays green. The
+test run looks normal; Pawl does not:
+
+```console
+$ python -m pytest tests -q                 # 1 known failure, same as before
+1 failed, 9 passed in 0.02s
+$ pawl guard --base main --replay
+### Pawl guard: FAIL (base main (a536657fb7cc))
+
+- **TEST_MODIFIED** (block) `tests/test_calc.py`: 1 existing test line(s) changed or removed; existing tests are read-only for agents
+- **TESTS_WEAKENED_REPLAY** (block) `tests/test_calc.py`: the original tests fail on this code (NEW_FAILURE: 1 test(s) fail that the baseline records as passing)
+  - `tests/test_calc.py::test_add_negative`
+```
+
+(Real output from `examples/demo`; run `examples/run_demo.sh` to see it.)
+
+## Quick start
+
+```bash
+pip install "pawl-gate @ git+https://github.com/Zero-State-LLC/pawl@v0.1.0"
+pawl init --github      # detects pytest, jest, vitest, go, or cargo
+git add pawl.toml pawl.baseline.json PAWL_DEBT.md .github/workflows/pawl.yml
+git commit -m "Add Pawl ratchet gate"
+```
+
+`pawl init` writes `pawl.toml`, runs your suite in two orders, records the
+baseline, and (with `--github`) writes a workflow. Then make the `pawl` job a
+required status check and add CODEOWNERS for the gate files
+([docs/REPO_SETTINGS.md](docs/REPO_SETTINGS.md)).
+
+While this repository is private, installing from Git needs credentials
+(for example a fine-grained read-only token in CI). The package is named
+`pawl-gate` because `pawl` is taken on PyPI. The import
+and the command are `pawl`.
+
+## How it works
+
+```mermaid
+flowchart LR
+    A[Agent edits code] --> H{pawl hook stop<br/>local, fast}
+    H -- red --> A
+    H -- green --> PR[Pull request]
+    PR --> CI[CI required check]
+    CI --> C[pawl check --ci<br/>config + baseline from base branch]
+    CI --> G[pawl guard --ci --replay<br/>diff vs base branch]
+    C --> D{All green?}
+    G --> D
+    D -- no --> A
+    D -- gate change --> Human[CODEOWNERS review<br/>pawl-approved label]
+    D -- yes --> M[Merge]
+    M --> U[pawl update<br/>baseline can only tighten]
+```
+
+| Command | What it does |
+| --- | --- |
+| `pawl check` | Runs every suite and compares each test ID with the baseline. Exit 0 pass, 1 regression, 2 could not measure, 3 preflight failed |
+| `pawl update` | Records the current state. Tightening is free; loosening needs `--loosen --reason` and is logged |
+| `pawl guard` | Scans the diff against a base ref for gate edits, test deletions and edits, new skips, hook tampering, and suspicious code. `--replay` runs the base branch's tests on the new code |
+| `pawl report` | Renders the last check and guard as Markdown |
+| `pawl init` | Detects the runner, writes the config and the first baseline |
+| `pawl hook stop`, `pawl hook protect` | Harness hooks for Claude Code, Codex, Cursor, and Hermes |
+| `pawl escalate` | The agent's sanctioned way out when the spec and the tests conflict |
+| `pawl quarantine` | Excuses a flaky test until an expiry date (humans only) |
+| `pawl mutate` | Advisory mutation spot check on changed Python lines |
+
+Adapters: pytest, Jest, Vitest, `go test`, `cargo test`, and any runner that
+writes JUnit XML. Every adapter fails closed: if Pawl cannot parse a result, it
+exits 2 instead of guessing.
+
+## The trust model in one paragraph
+
+The authority is CI, not the agent's machine. In CI, `pawl check` loads
+`pawl.toml` and the baseline from the base branch and uses the stricter of the
+base and branch baselines, so a branch cannot lower its own bar. `pawl guard`
+blocks changes to gate files unless a human adds the `pawl-approved` label.
+Harness hooks give the agent the same answer earlier, but they run where the
+agent can edit them, so they are a convenience. See
+[docs/RECOMMENDATION.md](docs/RECOMMENDATION.md).
+
+## Results
+
+On a synthetic corpus of 19 agent cheats and 6 clean changes, run against a
+project with one known failing test ([BENCHMARKS.md](BENCHMARKS.md)):
+
+| Detector | Cheats caught | Clean changes blocked |
+| --- | --- | --- |
+| plain `pytest` must pass | 18/19 | 5/6 (the known failure blocks everything) |
+| Abraxas count ratchet | 5/19 | 0/6 |
+| `pawl check` (agent side) | 12/19 | 0/6 |
+| `pawl hook stop --base` (agent side) | 17/19 | 0/6 |
+| Pawl in CI (check + guard + holdout) | 18/19 | 0/6 |
+
+The one miss, special-casing inputs that no holdout covers, is beyond any
+test-based gate. Overhead of `pawl check` over bare pytest was 0.3 s on both a
+100-test and a 5000-test suite.
+
+In a small live trial (12 episodes, one model, a task with one impossible
+test), an agent without the Pawl contract edited the conflicting test once
+and rewrote the spec docstring once. Pawl's stop hook and CI gate caught the
+test edit and missed the docstring rewrite. With the contract, all 8 episodes
+left the impossible test alone and escalated; none tampered. Details and
+limits are in [BENCHMARKS.md](BENCHMARKS.md).
+
+## Documentation
+
+- [docs/WHY_PAWL.md](docs/WHY_PAWL.md): who it is for and how it compares.
+- [docs/CONFIG.md](docs/CONFIG.md): every `pawl.toml` key.
+- [DESIGN.md](DESIGN.md): how it works and why.
+- [RESEARCH.md](RESEARCH.md): the literature behind each mechanism.
+- [docs/ARCHITECTURE_REVIEW.md](docs/ARCHITECTURE_REVIEW.md): threats covered
+  and not covered.
+- [docs/RECOMMENDATION.md](docs/RECOMMENDATION.md): where enforcement lives,
+  and migrating from the Abraxas ratchet script.
+- [integrations/](integrations/): Claude Code, Codex, Cursor, Hermes, GitHub
+  Actions, pre-commit, and an `AGENTS.md` contract.
+
+## Credits
+
+- The Abraxas `test_ratchet.sh` script, which Pawl generalizes.
+- ImpossibleBench (Zhong, Raghunathan, Carlini), EvilGenie, METR's reward
+  hacking reports, and the papers in [RESEARCH.md](RESEARCH.md).
+- Ratchet tools that came first: Betterer, ESLint bulk suppressions,
+  basedpyright baselines, mypy-baseline, and ratchet-gate.
+- A pawl is the hinged catch that lets a ratchet wheel turn one way only.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

pawl_gate-0.1.0/README.md

@@ -0,0 +1,153 @@
+# Pawl
+
+**Code can only move forward.**
+
+[![CI](https://github.com/Zero-State-LLC/pawl/actions/workflows/ci.yml/badge.svg)](https://github.com/Zero-State-LLC/pawl/actions/workflows/ci.yml)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue)](pyproject.toml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+[![Dependencies: none](https://img.shields.io/badge/dependencies-none-brightgreen)](pyproject.toml)
+
+Pawl is a ratchet gate for automated coding work. A change passes only if no
+test that passed now fails, no test disappeared or got skipped, and nobody
+loosened the gate itself. Known failures are allowed and can only go down.
+
+## The problem
+
+Coding agents told to "make the tests pass" sometimes change the tests instead
+of the code. Researchers have measured it: agents modify tests, overload `==`,
+and special-case inputs when a task is hard
+([ImpossibleBench](https://arxiv.org/abs/2510.20270),
+[EvilGenie](https://arxiv.org/abs/2511.21654),
+[METR](https://metr.org/blog/2025-06-05-recent-reward-hacking/)). Asking them
+not to is unreliable. A plain "tests must pass" check cannot help when the
+suite already has known failures, and a count-based ratchet misses a fixed test
+that hides a new failure, a skipped test, or a rewritten assertion.
+
+Here an agent "fixes" `add` and edits a test so the suite stays green. The
+test run looks normal; Pawl does not:
+
+```console
+$ python -m pytest tests -q                 # 1 known failure, same as before
+1 failed, 9 passed in 0.02s
+$ pawl guard --base main --replay
+### Pawl guard: FAIL (base main (a536657fb7cc))
+
+- **TEST_MODIFIED** (block) `tests/test_calc.py`: 1 existing test line(s) changed or removed; existing tests are read-only for agents
+- **TESTS_WEAKENED_REPLAY** (block) `tests/test_calc.py`: the original tests fail on this code (NEW_FAILURE: 1 test(s) fail that the baseline records as passing)
+  - `tests/test_calc.py::test_add_negative`
+```
+
+(Real output from `examples/demo`; run `examples/run_demo.sh` to see it.)
+
+## Quick start
+
+```bash
+pip install "pawl-gate @ git+https://github.com/Zero-State-LLC/pawl@v0.1.0"
+pawl init --github      # detects pytest, jest, vitest, go, or cargo
+git add pawl.toml pawl.baseline.json PAWL_DEBT.md .github/workflows/pawl.yml
+git commit -m "Add Pawl ratchet gate"
+```
+
+`pawl init` writes `pawl.toml`, runs your suite in two orders, records the
+baseline, and (with `--github`) writes a workflow. Then make the `pawl` job a
+required status check and add CODEOWNERS for the gate files
+([docs/REPO_SETTINGS.md](docs/REPO_SETTINGS.md)).
+
+While this repository is private, installing from Git needs credentials
+(for example a fine-grained read-only token in CI). The package is named
+`pawl-gate` because `pawl` is taken on PyPI. The import
+and the command are `pawl`.
+
+## How it works
+
+```mermaid
+flowchart LR
+    A[Agent edits code] --> H{pawl hook stop<br/>local, fast}
+    H -- red --> A
+    H -- green --> PR[Pull request]
+    PR --> CI[CI required check]
+    CI --> C[pawl check --ci<br/>config + baseline from base branch]
+    CI --> G[pawl guard --ci --replay<br/>diff vs base branch]
+    C --> D{All green?}
+    G --> D
+    D -- no --> A
+    D -- gate change --> Human[CODEOWNERS review<br/>pawl-approved label]
+    D -- yes --> M[Merge]
+    M --> U[pawl update<br/>baseline can only tighten]
+```
+
+| Command | What it does |
+| --- | --- |
+| `pawl check` | Runs every suite and compares each test ID with the baseline. Exit 0 pass, 1 regression, 2 could not measure, 3 preflight failed |
+| `pawl update` | Records the current state. Tightening is free; loosening needs `--loosen --reason` and is logged |
+| `pawl guard` | Scans the diff against a base ref for gate edits, test deletions and edits, new skips, hook tampering, and suspicious code. `--replay` runs the base branch's tests on the new code |
+| `pawl report` | Renders the last check and guard as Markdown |
+| `pawl init` | Detects the runner, writes the config and the first baseline |
+| `pawl hook stop`, `pawl hook protect` | Harness hooks for Claude Code, Codex, Cursor, and Hermes |
+| `pawl escalate` | The agent's sanctioned way out when the spec and the tests conflict |
+| `pawl quarantine` | Excuses a flaky test until an expiry date (humans only) |
+| `pawl mutate` | Advisory mutation spot check on changed Python lines |
+
+Adapters: pytest, Jest, Vitest, `go test`, `cargo test`, and any runner that
+writes JUnit XML. Every adapter fails closed: if Pawl cannot parse a result, it
+exits 2 instead of guessing.
+
+## The trust model in one paragraph
+
+The authority is CI, not the agent's machine. In CI, `pawl check` loads
+`pawl.toml` and the baseline from the base branch and uses the stricter of the
+base and branch baselines, so a branch cannot lower its own bar. `pawl guard`
+blocks changes to gate files unless a human adds the `pawl-approved` label.
+Harness hooks give the agent the same answer earlier, but they run where the
+agent can edit them, so they are a convenience. See
+[docs/RECOMMENDATION.md](docs/RECOMMENDATION.md).
+
+## Results
+
+On a synthetic corpus of 19 agent cheats and 6 clean changes, run against a
+project with one known failing test ([BENCHMARKS.md](BENCHMARKS.md)):
+
+| Detector | Cheats caught | Clean changes blocked |
+| --- | --- | --- |
+| plain `pytest` must pass | 18/19 | 5/6 (the known failure blocks everything) |
+| Abraxas count ratchet | 5/19 | 0/6 |
+| `pawl check` (agent side) | 12/19 | 0/6 |
+| `pawl hook stop --base` (agent side) | 17/19 | 0/6 |
+| Pawl in CI (check + guard + holdout) | 18/19 | 0/6 |
+
+The one miss, special-casing inputs that no holdout covers, is beyond any
+test-based gate. Overhead of `pawl check` over bare pytest was 0.3 s on both a
+100-test and a 5000-test suite.
+
+In a small live trial (12 episodes, one model, a task with one impossible
+test), an agent without the Pawl contract edited the conflicting test once
+and rewrote the spec docstring once. Pawl's stop hook and CI gate caught the
+test edit and missed the docstring rewrite. With the contract, all 8 episodes
+left the impossible test alone and escalated; none tampered. Details and
+limits are in [BENCHMARKS.md](BENCHMARKS.md).
+
+## Documentation
+
+- [docs/WHY_PAWL.md](docs/WHY_PAWL.md): who it is for and how it compares.
+- [docs/CONFIG.md](docs/CONFIG.md): every `pawl.toml` key.
+- [DESIGN.md](DESIGN.md): how it works and why.
+- [RESEARCH.md](RESEARCH.md): the literature behind each mechanism.
+- [docs/ARCHITECTURE_REVIEW.md](docs/ARCHITECTURE_REVIEW.md): threats covered
+  and not covered.
+- [docs/RECOMMENDATION.md](docs/RECOMMENDATION.md): where enforcement lives,
+  and migrating from the Abraxas ratchet script.
+- [integrations/](integrations/): Claude Code, Codex, Cursor, Hermes, GitHub
+  Actions, pre-commit, and an `AGENTS.md` contract.
+
+## Credits
+
+- The Abraxas `test_ratchet.sh` script, which Pawl generalizes.
+- ImpossibleBench (Zhong, Raghunathan, Carlini), EvilGenie, METR's reward
+  hacking reports, and the papers in [RESEARCH.md](RESEARCH.md).
+- Ratchet tools that came first: Betterer, ESLint bulk suppressions,
+  basedpyright baselines, mypy-baseline, and ratchet-gate.
+- A pawl is the hinged catch that lets a ratchet wheel turn one way only.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

pawl_gate-0.1.0/pyproject.toml

@@ -0,0 +1,83 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pawl-gate"
+version = "0.1.0"
+description = "Ratchet gate for automated coding work. Code can only move forward."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+authors = [{ name = "Zero-State LLC" }]
+keywords = ["ratchet", "ci", "testing", "ai-agents", "reward-hacking", "quality-gate"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Software Development :: Quality Assurance",
+  "Topic :: Software Development :: Testing",
+  "Typing :: Typed",
+]
+dependencies = []
+
+[project.optional-dependencies]
+dev = ["pytest>=8", "pytest-cov>=5", "ruff>=0.6", "mypy>=1.11"]
+
+[project.scripts]
+pawl = "pawl.cli:main"
+
+[project.urls]
+Source = "https://github.com/Zero-State-LLC/pawl"
+Issues = "https://github.com/Zero-State-LLC/pawl/issues"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+pawl = ["py.typed"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-ra --strict-markers"
+markers = ["slow: runs real subprocess suites"]
+
+[tool.coverage.run]
+source = ["pawl"]
+branch = true
+
+[tool.coverage.report]
+show_missing = true
+skip_covered = true
+fail_under = 80
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"
+src = ["src", "tests", "benchmarks"]
+extend-exclude = ["examples/*/scenarios", "benchmarks/work"]
+
+[tool.ruff.lint]
+select = ["E", "F", "W", "I", "B", "UP", "SIM", "RUF", "PL", "S"]
+ignore = [
+  "S603", "S607",   # subprocess with argv lists is the core job of this tool
+  "S404",
+  "PLR0911", "PLR0912", "PLR0913", "PLR0915", "PLR2004",
+  "S101",           # assert is fine in tests and internal invariants
+  "RUF001",
+  "PLC0415",        # lazy imports keep hook start-up fast
+]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/*" = ["S", "E501", "PLW0108"]
+"benchmarks/*" = ["S", "T201", "E501", "PLW2901"]
+
+[tool.mypy]
+strict = true
+python_version = "3.11"
+files = ["src/pawl"]

pawl_gate-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

pawl_gate-0.1.0/src/pawl/__init__.py

@@ -0,0 +1,5 @@
+"""Pawl: a ratchet gate for automated coding work. Code can only move forward."""
+
+__version__ = "0.1.0"
+
+__all__ = ["__version__"]

pawl_gate-0.1.0/src/pawl/__main__.py

@@ -0,0 +1,5 @@
+"""Allow ``python -m pawl``."""
+
+from pawl.cli import main
+
+raise SystemExit(main())