probity-ratchet 0.1.0__tar.gz

probity_ratchet-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,82 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  UV_PYTHON: "3.14"
+  UV_LOCKED: "1"
+
+jobs:
+  lint:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 20
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - run: uv sync --all-groups --all-extras
+      - run: uv run ruff check
+      - run: uv run ruff format --check
+      - run: uv run mypy src
+      - run: python3 scripts/readme-lint.py README.md
+      # check-docs imports ratchet.cases to count the case families, so it runs inside the synced virtualenv
+      - run: uv run python scripts/check-docs.py
+
+  test:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 45
+    services:
+      # Same image, credentials and port mapping as docker/compose.yaml; the "image tag matches compose" step fails the
+      # job if the two drift apart.
+      atlas:
+        image: mongodb/mongodb-atlas-local:8.3.9-20260928T091948Z
+        env:
+          MONGODB_INITDB_ROOT_USERNAME: ratchet
+          MONGODB_INITDB_ROOT_PASSWORD: ratchet-local-dev
+        ports:
+          - 127.0.0.1:27018:27017
+        options: >-
+          --hostname ratchet-atlas
+          --ulimit nofile=1048576:1048576
+          --health-cmd "mongosh -u ratchet -p ratchet-local-dev --quiet --eval 1"
+          --health-interval 5s
+          --health-timeout 10s
+          --health-retries 30
+          --health-start-period 20s
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - name: image tag matches compose
+        run: |
+          want=$(sed -n 's/^ *image: *//p' docker/compose.yaml | head -1)
+          have=$(sed -n 's/^ *image: *\(mongodb\/mongodb-atlas-local:[^ ]*\).*$/\1/p' .github/workflows/ci.yml | head -1)
+          echo "compose: $want  workflow: $have"
+          test -n "$want" && test "$want" = "$have"
+      - name: wait until mongot answers search-index calls
+        run: |
+          id=$(docker ps --filter ancestor="$(sed -n 's/^ *image: *//p' docker/compose.yaml | head -1)" --format '{{.ID}}' | head -1)
+          test -n "$id"
+          for i in $(seq 1 90); do
+            if docker exec "$id" mongosh -u ratchet -p ratchet-local-dev --quiet --eval "db.getSiblingDB('healthprobe').nothing.aggregate([{\$listSearchIndexes:{}}]).toArray().length" >/dev/null 2>&1; then
+              echo "search ready after $((i * 5)) s"; exit 0
+            fi
+            sleep 5
+          done
+          docker logs --tail 50 "$id"
+          exit 1
+      - run: uv sync --all-groups --all-extras
+      # Default selection: sandbox tests (hackathon cluster secrets) and live tests (VOYAGE_API_KEY) are deselected.
+      - name: pytest
+        run: >-
+          uv run --with pytest-timeout python -m pytest -q -W error --timeout=120 -rfEs --tb=short
+          -m "not sandbox and not live"
+          --cov=src/ratchet --cov-report=term-missing:skip-covered

probity_ratchet-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+# Private strategy, captures and research never enter this public repository.
+captures/
+research/
+private/
+.venv/
+__pycache__/
+*.pyc
+.env
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+htmlcov/
+.coverage
+.claude_correlation/

probity_ratchet-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.

probity_ratchet-0.1.0/PKG-INFO

@@ -0,0 +1,96 @@
+Metadata-Version: 2.5
+Name: probity-ratchet
+Version: 0.1.0
+Summary: An agent harness that turns each failure into a proven guard or procedure, with every version and proof kept in MongoDB Atlas.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: agent-evidence-vectors==0.17.7
+Requires-Dist: cryptography>=44
+Requires-Dist: httpx>=0.27
+Requires-Dist: probity-verify==0.1.0
+Requires-Dist: pymongo>=4.10
+Requires-Dist: raindrop-ai==0.0.75
+Requires-Dist: rich>=15.0.0
+Provides-Extra: bench
+Requires-Dist: agentdojo==0.1.35; extra == 'bench'
+Requires-Dist: audioop-lts==0.2.2; (python_full_version >= '3.13') and extra == 'bench'
+Requires-Dist: litellm==1.102.1; extra == 'bench'
+Requires-Dist: tau-bench; extra == 'bench'
+Requires-Dist: tau2; extra == 'bench'
+Requires-Dist: terminal-bench==0.2.18; extra == 'bench'
+Requires-Dist: tool-sandbox; extra == 'bench'
+Provides-Extra: gepa
+Requires-Dist: gepa==0.1.4; extra == 'gepa'
+Description-Content-Type: text/markdown
+
+# Ratchet
+
+Ratchet turns an AI agent's mistakes into tested, signed safety rules, and refuses any change it cannot prove.
+
+When an agent fails, Ratchet writes a guard: a small rule that checks each tool call before it runs. It adopts the guard only after a replay (rerunning recorded past conversations through it) and fresh tests on held-out cases (test cases the improver never sees). Each decision is a receipt, a signed record anyone can verify offline.
+
+It is for teams running tool-using agents that touch money, accounts or tickets, and need a fix to a failing agent to be proven before it ships.
+
+## Install
+
+```sh
+git clone --branch v0.1.0 https://github.com/probityai/ratchet && cd ratchet
+uv sync
+```
+
+Python 3.12 or later. The guard sandbox needs Linux.
+
+## Try it in 30 seconds
+
+No database, no model key. This guard stops force pushes to `main`. It is a single standard-library file, exported from an admitted guard, and it is a Claude Code hook (a script run before each tool call). It denies the call:
+
+```sh
+echo '{"hook_event_name": "PreToolUse", "tool_name": "Bash", "cwd": ".", "tool_input": {"command": "git push --force origin main"}}' \
+  | python3 examples/claude-code/hooks/ratchet_no_force_push_main.py; echo "exit $?"
+```
+
+```text
+blocked by guard no-force-push-main: force push to main rewrites shared history; push a branch and open a pull request instead
+{"hookSpecificOutput": {"hookEventName": "PreToolUse", "permissionDecision": "deny", "permissionDecisionReason": "blocked by guard no-force-push-main: force push to main rewrites shared history; push a branch and open a pull request instead"}}exit 2
+```
+
+Before it was exported, the guard was replayed over six recorded Claude Code sessions: it fired on the three calls it was written for and on none of the other twelve (`examples/claude-code/replay.json`). The hook's header names the receipt (the signed decision) that admitted it; `uv run python -m ratchet.export.claude_code --verify examples/claude-code/hooks/ratchet_no_force_push_main.py` checks that receipt.
+
+## What it does
+
+A support agent works in a simulated company: a billing provider, tickets, approvals and mail. Its eight case families are seven kinds of trap, each with benign twins (matching cases where the action is allowed, so a rule that blocks them fails), plus ordinary requests that must succeed. Every case is graded on the final state of every system, never on the agent's words.
+
+When the agent fails, the improver proposes a guard or a procedure (written steps for the agent). A change is adopted only if four checks pass: replay; fresh paired tests on held-out cases against the parent harness (the code around the model: prompt, tools and rules); no growth of the agent's authority; and a signed receipt, which verifies offline against a pinned public key. The gates are in [docs/ADMISSION.md](docs/ADMISSION.md). Every version, trace, evaluation and decision, rejections included, lives in MongoDB Atlas.
+
+## Status
+
+Version 0.1.0, built on 2026-10-11 at the MongoDB harness hackathon. The suite, graders and rule are frozen before each run. Measured results, with denominators, are in [docs/RESULTS.md](docs/RESULTS.md).
+
+## Docs
+
+| Page | What is in it |
+|---|---|
+| [Running](docs/RUNNING.md) | Local Atlas, environment and every command |
+| [Admission rule](docs/ADMISSION.md) | The gates in plain words |
+| [Architecture](docs/ARCHITECTURE.md) | Packages, guard sandbox, storage |
+| [Verifying a decision](docs/VERIFY.md) | Check a receipt offline |
+| [Results](docs/RESULTS.md) | Every measured result and its records |
+| [Claude Code hook](examples/claude-code/README.md) | Prove a guard on your own sessions, then install it |
+| [Build contract](docs/CONTRACT.md) | Types, lane interfaces and the full admission rule |
+
+## Built today and reused
+
+The repository's first commit is from 2026-10-11, and everything under `src/ratchet`, `tests`, `examples` and `docs` was written at the event. The rest is a pinned dependency or a service.
+
+| Reused | Pin |
+|---|---|
+| Runtime | `pymongo>=4.10`, `httpx>=0.27`, `cryptography>=44`, `rich>=15`, `raindrop-ai==0.0.75` |
+| Earlier work of the same authors | `probity-verify` at commit `b920366`, `agent-evidence-vectors==0.17.7` |
+| Benchmark extra | `agentdojo==0.1.35` (tool outputs carry hidden prompt-injection attacks), `litellm==1.102.1`, `terminal-bench==0.2.18`, `tau-bench` at `59a200c` (simulated customer-service tasks graded on the final database state), `tau2` at `4ce7c03`, `tool-sandbox` at `c8571d7` |
+| Instruction search extra | `gepa==0.1.4` |
+| Services | MongoDB Atlas (`mongodb-atlas-local:8.3.9-20260928T091948Z` for development), Voyage embeddings, Raindrop |
+
+The integration that writes and checks Ratchet's own admission records is new. The verifier it calls is not.
+
+License: Apache-2.0.

probity_ratchet-0.1.0/README.md

@@ -0,0 +1,70 @@
+# Ratchet
+
+Ratchet turns an AI agent's mistakes into tested, signed safety rules, and refuses any change it cannot prove.
+
+When an agent fails, Ratchet writes a guard: a small rule that checks each tool call before it runs. It adopts the guard only after a replay (rerunning recorded past conversations through it) and fresh tests on held-out cases (test cases the improver never sees). Each decision is a receipt, a signed record anyone can verify offline.
+
+It is for teams running tool-using agents that touch money, accounts or tickets, and need a fix to a failing agent to be proven before it ships.
+
+## Install
+
+```sh
+git clone --branch v0.1.0 https://github.com/probityai/ratchet && cd ratchet
+uv sync
+```
+
+Python 3.12 or later. The guard sandbox needs Linux.
+
+## Try it in 30 seconds
+
+No database, no model key. This guard stops force pushes to `main`. It is a single standard-library file, exported from an admitted guard, and it is a Claude Code hook (a script run before each tool call). It denies the call:
+
+```sh
+echo '{"hook_event_name": "PreToolUse", "tool_name": "Bash", "cwd": ".", "tool_input": {"command": "git push --force origin main"}}' \
+  | python3 examples/claude-code/hooks/ratchet_no_force_push_main.py; echo "exit $?"
+```
+
+```text
+blocked by guard no-force-push-main: force push to main rewrites shared history; push a branch and open a pull request instead
+{"hookSpecificOutput": {"hookEventName": "PreToolUse", "permissionDecision": "deny", "permissionDecisionReason": "blocked by guard no-force-push-main: force push to main rewrites shared history; push a branch and open a pull request instead"}}exit 2
+```
+
+Before it was exported, the guard was replayed over six recorded Claude Code sessions: it fired on the three calls it was written for and on none of the other twelve (`examples/claude-code/replay.json`). The hook's header names the receipt (the signed decision) that admitted it; `uv run python -m ratchet.export.claude_code --verify examples/claude-code/hooks/ratchet_no_force_push_main.py` checks that receipt.
+
+## What it does
+
+A support agent works in a simulated company: a billing provider, tickets, approvals and mail. Its eight case families are seven kinds of trap, each with benign twins (matching cases where the action is allowed, so a rule that blocks them fails), plus ordinary requests that must succeed. Every case is graded on the final state of every system, never on the agent's words.
+
+When the agent fails, the improver proposes a guard or a procedure (written steps for the agent). A change is adopted only if four checks pass: replay; fresh paired tests on held-out cases against the parent harness (the code around the model: prompt, tools and rules); no growth of the agent's authority; and a signed receipt, which verifies offline against a pinned public key. The gates are in [docs/ADMISSION.md](docs/ADMISSION.md). Every version, trace, evaluation and decision, rejections included, lives in MongoDB Atlas.
+
+## Status
+
+Version 0.1.0, built on 2026-10-11 at the MongoDB harness hackathon. The suite, graders and rule are frozen before each run. Measured results, with denominators, are in [docs/RESULTS.md](docs/RESULTS.md).
+
+## Docs
+
+| Page | What is in it |
+|---|---|
+| [Running](docs/RUNNING.md) | Local Atlas, environment and every command |
+| [Admission rule](docs/ADMISSION.md) | The gates in plain words |
+| [Architecture](docs/ARCHITECTURE.md) | Packages, guard sandbox, storage |
+| [Verifying a decision](docs/VERIFY.md) | Check a receipt offline |
+| [Results](docs/RESULTS.md) | Every measured result and its records |
+| [Claude Code hook](examples/claude-code/README.md) | Prove a guard on your own sessions, then install it |
+| [Build contract](docs/CONTRACT.md) | Types, lane interfaces and the full admission rule |
+
+## Built today and reused
+
+The repository's first commit is from 2026-10-11, and everything under `src/ratchet`, `tests`, `examples` and `docs` was written at the event. The rest is a pinned dependency or a service.
+
+| Reused | Pin |
+|---|---|
+| Runtime | `pymongo>=4.10`, `httpx>=0.27`, `cryptography>=44`, `rich>=15`, `raindrop-ai==0.0.75` |
+| Earlier work of the same authors | `probity-verify` at commit `b920366`, `agent-evidence-vectors==0.17.7` |
+| Benchmark extra | `agentdojo==0.1.35` (tool outputs carry hidden prompt-injection attacks), `litellm==1.102.1`, `terminal-bench==0.2.18`, `tau-bench` at `59a200c` (simulated customer-service tasks graded on the final database state), `tau2` at `4ce7c03`, `tool-sandbox` at `c8571d7` |
+| Instruction search extra | `gepa==0.1.4` |
+| Services | MongoDB Atlas (`mongodb-atlas-local:8.3.9-20260928T091948Z` for development), Voyage embeddings, Raindrop |
+
+The integration that writes and checks Ratchet's own admission records is new. The verifier it calls is not.
+
+License: Apache-2.0.

probity_ratchet-0.1.0/docker/compose.yaml

@@ -0,0 +1,31 @@
+# Local Atlas (mongod + mongot) for development and tests: Atlas Search and Vector Search work offline.
+# Single-node replica set, so change streams and transactions work. Start: docker compose -f docker/compose.yaml up -d --wait
+services:
+  atlas:
+    image: mongodb/mongodb-atlas-local:8.3.9-20260928T091948Z
+    container_name: ratchet-atlas
+    hostname: ratchet-atlas
+    ports:
+      - "127.0.0.1:27018:27017"
+    environment:
+      MONGODB_INITDB_ROOT_USERNAME: ratchet
+      MONGODB_INITDB_ROOT_PASSWORD: ratchet-local-dev
+    # WiredTiger keeps a file per collection and index; the default limit panics mongod under test load
+    ulimits:
+      nofile:
+        soft: 1048576
+        hard: 1048576
+    volumes:
+      - ratchet-atlas-data:/data/db
+      - ratchet-atlas-config:/data/configdb
+    # healthy means mongod AND the search service (mongot) answer, so search-index calls work at once
+    healthcheck:
+      test: ["CMD", "mongosh", "-u", "ratchet", "-p", "ratchet-local-dev", "--quiet", "--eval", "db.getSiblingDB('healthprobe').nothing.aggregate([{$$listSearchIndexes:{}}]).toArray().length"]
+      interval: 5s
+      timeout: 10s
+      retries: 30
+      start_period: 20s
+
+volumes:
+  ratchet-atlas-data:
+  ratchet-atlas-config:

probity_ratchet-0.1.0/docs/ADMISSION.md

@@ -0,0 +1,59 @@
+# The admission rule, in plain words
+
+Ratchet changes an agent's harness only when the change has passed every check below. This page is the
+short version; the exact rule is in [CONTRACT.md](CONTRACT.md).
+
+A change is a **guard** (code that blocks a tool call), a **procedure** (written steps), or a **prompt
+section**. The agent being improved is the **parent**. The changed version is the **candidate**.
+
+## Before anything runs
+
+The cases, graders, fault schedules, model configuration, evaluator version, replay snapshot and proposal
+budgets are frozen and digested. A candidate is frozen before it is evaluated. If any of these changes, that is a new
+version, and old results are history, not evidence for the new one.
+
+## The checks
+
+| # | Check | In plain words |
+|---|---|---|
+| 1 | **Structure and authority** | A change may add guards, procedures and prompt sections, and may shrink the tool list. Existing guards and procedures stay, in order. Existing prompt bytes stay a prefix. Tools can only be removed. A human-signed exception is a separate record, not an ordinary admission |
+| 2 | **Replay** | Each new guard has declared target failures. Using each call's recorded inputs (the call, the state before it, the history before it), the guard must fire on every target at or before the step that caused it, and on no passing trace and no benign twin. Each guard is replayed alone and all guards composed. The whole snapshot is replayed even after a first counterexample; an error or incomplete coverage cannot clear a guard |
+| 3 | **Fresh evaluation** | The parent runs twice and the candidate runs twice on the same held-out cases. A *stable recovery* fails both parent runs and passes both candidate runs: at least two are needed. Every case the parent passed in either run must pass in both candidate runs. No must-succeed regression, and no intervention on a benign twin. All four outcome vectors, the parent's run-to-run disagreement and costs are recorded |
+| 4 | **Overfitting screen** | No case, customer, charge or order identifier, and no copied name or amount, from the fixtures may appear in the change |
+| 5 | **A signed receipt** | The decision binds the candidate, the parent, the policy and evaluator versions, the manifests and every report, and is signed before the change is activated |
+
+Cost is recorded in every decision. It is not a gate.
+
+## What the evidence does and does not show
+
+- **Replay** shows how a guard behaves on recorded inputs. It does not show that the run would have
+  succeeded after the block, so every kind of change also needs fresh evaluation.
+- **Fresh evaluation** shows what the evaluated cases did. It is finite, and neither check proves a change safe in general.
+- **Tool-list monotonicity** is an enforced policy over named capabilities, not a proof of safety.
+- **A signature** shows who signed which decision with which evidence digests. It does not show the evaluator was honest.
+- Every decision lists exactly what was checked, with counts and case ids, and rejected decisions are kept.
+
+## Labels you will see
+
+| Label | Meaning |
+|---|---|
+| FRESH | every model call was answered fresh; the only mode that counts as evidence |
+| RECORDED | a stored fresh result shown again, with its timestamp |
+| CACHED | a byte-identical response replay, for debugging only; never evidence |
+
+## Who can see what
+
+Held-out cases and their traces live in a database the improver's identity cannot read. The improver receives
+a sanitized report schema, never protected case ids, raw inputs or per-case outcomes. A final audit cohort is
+unused until the harness is frozen.
+
+## Activation
+
+Admission and activation are separate. Activation is one idempotent database transaction that checks the
+receipt and the expected active version, so a stale or missing receipt cannot activate a change.
+
+## The improver's own instructions
+
+The improver's instructions are versioned too. Two frozen versions are scored on separately held-out
+proposal tasks with the same budget, and counted for invalid, duplicate, rejected and empty proposals. Each
+counted candidate must independently pass the checks above.

probity_ratchet-0.1.0/docs/ARCHITECTURE.md

@@ -0,0 +1,85 @@
+# Architecture
+
+## The loop
+
+```
+failures --> diagnose --> propose --> replay --> fresh evaluation --> admit --> sign --> activate
+   ^                                                                                          |
+   +------------------------------------- the new harness runs the next cases <------------------+
+```
+
+1. The worker runs cases under the active harness and records every event as a trace.
+2. The improver clusters the failures and proposes guards, procedures and prompt sections. It sees
+   training material only, plus lessons retrieved from earlier attempts on similar failures.
+3. Each guard is replayed over the recorded traces. No model is called.
+4. Candidates that survive run on held-out cases, with the parent run twice and the candidate run twice.
+5. The admission rule decides. The decision, with its evidence digests, is signed.
+6. Activation moves the active-version pointer in one database transaction that checks the receipt.
+
+## Packages (`src/ratchet`)
+
+| Package | Job |
+|---|---|
+| `world` | The simulated company: billing provider, payments, orders, subscriptions, tickets, approvals, mail, policy, and a fault layer that can lose a reply after the action committed |
+| `cases` | Eight case families, trap cases, benign twins and must-succeed cases, split into train, held-out and audit, with graders that read the final state of every system. `FROZEN.sha256` pins the suite |
+| `agent` | The harness bundle, the worker loop, the guard runtime, the chat-completions model client |
+| `store` | Atlas persistence: versions, runs, traces, evaluations, decisions, failure memory, checkpoints, change streams, and the database roles that keep the improver away from held-out cases |
+| `improve` | Diagnosis, proposal, replay, the admission rule, receipts, activation, the version archive, retrieval of similar failures, and the search over the improver's own instructions |
+| `verify` | Independent checking of a receipt through the pinned verifier and a pinned key |
+| `export` | Admitted guards as Claude Code hooks, and replay of a guard over Claude Code session transcripts |
+| `view` | The terminal views and the static report: replay matrix, lineage, trace, decision, live change stream |
+| `bench` | Adapters that run the same loop on public agent benchmarks, plus cross-model transfer runs; the measured results are in [RESULTS.md](RESULTS.md) |
+| `telemetry` | An optional sink that sends runs, evaluations and decisions to Raindrop |
+| `atlas_features` | Probes that run an Atlas capability on the cluster before the product claims it; the results are in [the probe page](results/atlas-probes.md) |
+
+## The guard sandbox
+
+A guard is untrusted model output. Its source defines `check(call, view, history)` and returns a reason
+string to block or `None` to allow. Each guard runs in its own child process (`python -I -S`, empty
+environment) that applies, before it reads the source:
+
+- resource limits for CPU, memory and time,
+- a new network namespace with no network,
+- a seccomp filter,
+- a Landlock file-system ruleset.
+
+The child reports which layers took effect, and the runtime refuses to start one that lacks a required layer.
+Every evaluation re-executes the module source, so a guard carries no state from one call to the next and a
+replay gives the same answer as the live run. A guard that fails to compile, raises, returns something other
+than a string, runs too long or kills its process blocks the call, and the error is recorded.
+
+## What the store keeps
+
+| Collection | Holds |
+|---|---|
+| `harness_versions` | Every version, its parent and its digest. A read recomputes the digest and rejects a mismatch |
+| `runs`, `traces`, `trace_chunks` | One trace per document, with events embedded. A trace over 4 MB splits into ordered chunks, and its header is written last, so a crash leaves no half-visible trace |
+| `evals` | Evaluation reports, each labelled FRESH, RECORDED or CACHED |
+| `decisions` | Every admission decision, rejections included, with checks, evidence and the signed envelope |
+| `failures` | Failure summaries with embeddings, searched by vector similarity |
+| `checkpoints` | The state after each committed world call, so a killed run resumes without repeating a side effect |
+| `embedding_cache` | Embeddings keyed by content |
+| `cases` (held-out database) | Held-out cases, in a separate database that the improver's role has no privilege on |
+
+Every write is idempotent. A second write of the same document is a no-op, and a second write of different
+content under the same id raises an error instead of replacing history.
+
+## What the improver is allowed to see
+
+| Material | Improver | Evaluator |
+|---|---|---|
+| Training cases and traces | yes | yes |
+| Replay results on training traces | yes | yes |
+| Held-out cases and per-case outcomes | no | yes |
+| Final audit cohort | no, until the harness is frozen | yes |
+| Admin and evaluator credentials | no | yes |
+
+The improver's database user holds the working database and nothing on held-out cases. The boundary is a
+server-side role, so a bug in Ratchet's code cannot widen it.
+
+## Receipts
+
+A decision is canonical JSON, wrapped in a DSSE envelope and signed with Ed25519. The receipt names the
+candidate, the parent, the policy and evaluator versions, the corpus snapshot and every report digest.
+`ratchet verify` and `python -m ratchet.verify` check it against a public key that was pinned before the
+receipt existed. [VERIFY.md](VERIFY.md) lists the pins.