ratchet-size 0.1.0__tar.gz

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

ratchet_size-0.1.0/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.4
+Name: ratchet-size
+Version: 0.1.0
+Summary: A code-size budget that only goes down: keeps coding agents from bloating your repo.
+Author: Krishan Subudhi
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/krishansubudhi/ratchet
+Project-URL: Repository, https://github.com/krishansubudhi/ratchet
+Project-URL: Issues, https://github.com/krishansubudhi/ratchet/issues
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
+Dynamic: license-file
+
+# ratchet
+
+[![CI](https://github.com/krishansubudhi/ratchet/actions/workflows/ci.yml/badge.svg)](https://github.com/krishansubudhi/ratchet/actions/workflows/ci.yml)
+
+**A code-size budget that only goes down.** Coding agents are good at adding
+code and bad at deciding not to. `ratchet` gives the repo a line budget:
+growth past the ceiling is refused, in plain words the agent can act on, and
+only a human can raise it.
+
+![ratchet refusing a duplicated-code change on pallets/click, then passing once the duplicate is removed](docs/demo.gif)
+
+Real run, on [pallets/click](https://github.com/pallets/click): `ratchet init`
+records today's size; an agent asked for a feature pastes a near-duplicate of
+existing code instead of reusing it; `ratchet check` refuses the growth and
+says exactly why; the duplicate goes, and the check passes again. Real
+commands and output: [docs/examples.md](docs/examples.md). (The bloat step
+is a scripted patch standing in for the agent, honestly -- see the caption
+there.)
+
+## Quickstart
+
+1. **Install:** `pipx install ratchet-size` (or `pip install ratchet-size`,
+   or `pip install -e .` from a clone).
+2. **Record today's size:** `ratchet init` -- writes `.ratchet.json`; commit it.
+3. **Wire up your agent:** paste this sentence to it: *"Set up ratchet in
+   /path/to/repo by following
+   https://github.com/krishansubudhi/ratchet/blob/main/SETUP-FOR-AGENTS.md"*
+
+That's it. Everything past this point is detail you can come back to: what
+counts as a line, the four rules, grants, config, and per-harness
+integrations.
+
+## Claude Code plugin
+
+Prefer a plugin over the manual setup above? Ratchet ships as a Claude Code
+plugin, with this repo doubling as its own marketplace:
+
+```text
+/plugin marketplace add krishansubudhi/ratchet
+/plugin install ratchet@ratchet
+```
+
+That installs a **Stop** hook (`ratchet check --hook`, falling back to `uvx`
+if `ratchet` isn't on `PATH` yet) so Claude Code can't end a turn with the
+repo over budget, plus a `/ratchet:setup` command that runs the
+[agent setup](SETUP-FOR-AGENTS.md) -- install, `ratchet init`, detect your
+harness, `ratchet check` -- in the repo you're in. See
+[`.claude-plugin/`](.claude-plugin) and [`hooks/hooks.json`](hooks/hooks.json)
+for the manifests, or `claude plugin validate .` to check them yourself.
+
+## What it counts
+
+**Scope:** the one git repository you run it in (`git rev-parse
+--show-toplevel`). Other repos on the machine are never touched, and each
+repo gets its own `.ratchet.json`.
+
+**Which files:** git-tracked files, plus untracked files that aren't
+gitignored, whose extension is one of the code extensions present at
+`init` (`.py`, `.js`, `.ts`, `.go`, `.rs`, `.java`, `.rb`, `.c`, `.sh`, and
+more -- see `CODE_EXTS` in `ratchet/measure.py`). Blank lines don't count.
+
+**Source vs tests:** a file matching a test glob (`test_*`, `*_test.*`,
+`*_tests.*`, `*.test.*`, `*.spec.*`, or living under `tests/`, `test/`,
+`__tests__/`, `spec/`) is `tests`; everything else is `source`. Both groups
+are plain config in `.ratchet.json` -- edit `include`/`exclude`/`extensions`
+to carve out a different split, e.g. `"exclude": ["vendor/**", "**/*.gen.*"]`
+to stop counting vendored or generated code.
+
+**Existing repo:** `ratchet init` measures today's totals and sets the
+ceilings there (plus optional `--slack`). A file already over
+`max_file_lines` is frozen at its current size, so nothing is refused on
+day one -- you start where you are. From then on a ceiling may only shrink,
+unless a human runs `ratchet grant`.
+
+## What the agent sees when refused
+
+```
+ratchet: REFUSED -- 2 problems (source 10,412/10,300, tests 4,980/5,000)
+
+1. source is 10,412 lines, ceiling 10,300: 112 over
+   grew vs HEAD: app/api.py +80, app/store.py +40
+   fix: remove at least 112 lines of source: delete dead code, reuse what
+   exists instead of adding a parallel version, simplify.
+2. app/api.py is 431 lines, limit 400
+   seams near the middle: line 198 `def upload`, line 230 `class Session`
+   fix: split it at a seam: move a cohesive group of definitions into a new
+   file, so each piece is under 400 lines.
+
+Do not edit .ratchet.json or .ratchet-grants.jsonl to get past this.
+If the growth is truly needed, stop and ask a human to run:
+  ratchet grant +112 --group source --reason "<why>" --by <name>
+  ratchet grant +31 --file app/api.py --reason "<why>" --by <name>
+```
+
+Every refusal says what grew, by how much, and which fix applies: shrink,
+split, or ask a human. For a harness, `ratchet check --json` gives the same
+result as data.
+
+## The four rules
+
+| Rule | What it does |
+|------|--------------|
+| **Budget** | Each group (`source`, `tests` by default) has a ceiling. A total over it is refused. |
+| **Seams** | A file over `max_file_lines` (default 400) is refused, with the top-level definitions nearest the middle offered as places to cut. A file already over the limit at `init` is recorded at its size: it may shrink, never grow. |
+| **Grants** | Only `ratchet grant` raises a limit, and every grant is appended to `.ratchet-grants.jsonl` with who and why. |
+| **Tighten** | `ratchet tighten` lowers every ceiling to the measured size (plus optional `slack`). Nothing ever raises it automatically. |
+
+Lines are counted without blanks. Docs, data, and fixtures don't count: only
+files whose extensions you list in `.ratchet.json` do.
+
+## How grants work
+
+Sometimes the growth is the point: a real feature, a new integration. Then a
+human runs:
+
+```sh
+ratchet grant +300 --group source --reason "CSV export (issue 41)" --by alice
+ratchet grant +60 --file app/api.py --reason "until the router split lands" --by alice
+```
+
+That raises the ceiling in `.ratchet.json` and appends a line to
+`.ratchet-grants.jsonl`:
+
+```json
+{"after": 10600, "before": 10300, "by": "alice", "lines": 300, "reason": "CSV export (issue 41)", "target": "source", "ts": "2026-01-15T09:30:00Z"}
+```
+
+Commit both files. Here is what keeps grants honest:
+
+- **In CI, run `ratchet check --base <target branch>`.** It refuses any ceiling
+  that is higher than the base's unless grants appended since the base pay for
+  it. An agent that edits `.ratchet.json` by hand passes locally and fails
+  review. The check also refuses a grants log that was rewritten rather than
+  appended to.
+- Grants are one-line diffs in the pull request, so a reviewer sees them.
+- Tell your agent never to run `ratchet grant`. The Claude Code integration
+  also puts it on the permission deny list.
+
+Run `ratchet tighten` after a cleanup and commit the result. The room you
+freed is now the new ceiling.
+
+## Running it by hand
+
+`ratchet check` exits `0` when the repo is within budget, `1` when refused,
+`2` on a setup error (bad config, not a git repo when `--base` is used, and
+so on). `python -m ratchet` works the same as the `ratchet` entry point, if
+you don't have it on `PATH`.
+
+## Integrations
+
+| Harness | How |
+|---------|-----|
+| Claude Code | Stop hook `ratchet check --hook`: [integrations/claude-code](integrations/claude-code/README.md) |
+| Cursor, Codex CLI, aider | instruction file + git hook / test-cmd: [integrations/other-agents.md](integrations/other-agents.md) |
+| pre-commit | framework hook, or a plain git hook: [integrations/pre-commit](integrations/pre-commit/README.md) |
+| GitHub Actions | `uses: krishansubudhi/ratchet@v0`: [integrations/github](integrations/github/README.md) |
+| Anything else | prompt snippet: [integrations/any-agent.md](integrations/any-agent.md) |
+
+## Configuration
+
+`ratchet init` writes `.ratchet.json`. It is JSON because ratchet must write
+the file, and Python's standard library reads TOML but cannot write it.
+
+```json
+{
+  "version": 1,
+  "max_file_lines": 400,
+  "slack": 0,
+  "groups": {
+    "source": {"include": ["**"], "exclude": ["**/tests/**", "**/test_*"], "extensions": [".py", ".ts"]},
+    "tests":  {"include": ["**/tests/**", "**/test_*"], "extensions": [".py", ".ts"]}
+  },
+  "ceilings": {"source": 10300, "tests": 5000},
+  "file_ceilings": {"app/legacy.py": 1210}
+}
+```
+
+- Globs work like gitignore: `**/` means any number of directories.
+- Each file belongs to the first group that matches it.
+- `slack` keeps some headroom above the measured size after `init` and
+  `tighten`, if you would rather not require a delete for every add.
+- Files are listed with `git ls-files`, so ignored files never count.
+  Outside git, ratchet walks the tree and skips the usual build and vendor
+  directories.
+
+`ratchet init --max-file-lines 300 --slack 50` sets both at creation.
+
+## Requirements
+
+Python 3.10+, git (optional, needed for `--base` and the "grew vs" lines). No
+dependencies. Tests: `pip install pytest && python -m pytest -q`.
+
+## License
+
+Apache-2.0. Copyright 2026 Krishan Subudhi.

ratchet_size-0.1.0/README.md

@@ -0,0 +1,195 @@
+# ratchet
+
+[![CI](https://github.com/krishansubudhi/ratchet/actions/workflows/ci.yml/badge.svg)](https://github.com/krishansubudhi/ratchet/actions/workflows/ci.yml)
+
+**A code-size budget that only goes down.** Coding agents are good at adding
+code and bad at deciding not to. `ratchet` gives the repo a line budget:
+growth past the ceiling is refused, in plain words the agent can act on, and
+only a human can raise it.
+
+![ratchet refusing a duplicated-code change on pallets/click, then passing once the duplicate is removed](docs/demo.gif)
+
+Real run, on [pallets/click](https://github.com/pallets/click): `ratchet init`
+records today's size; an agent asked for a feature pastes a near-duplicate of
+existing code instead of reusing it; `ratchet check` refuses the growth and
+says exactly why; the duplicate goes, and the check passes again. Real
+commands and output: [docs/examples.md](docs/examples.md). (The bloat step
+is a scripted patch standing in for the agent, honestly -- see the caption
+there.)
+
+## Quickstart
+
+1. **Install:** `pipx install ratchet-size` (or `pip install ratchet-size`,
+   or `pip install -e .` from a clone).
+2. **Record today's size:** `ratchet init` -- writes `.ratchet.json`; commit it.
+3. **Wire up your agent:** paste this sentence to it: *"Set up ratchet in
+   /path/to/repo by following
+   https://github.com/krishansubudhi/ratchet/blob/main/SETUP-FOR-AGENTS.md"*
+
+That's it. Everything past this point is detail you can come back to: what
+counts as a line, the four rules, grants, config, and per-harness
+integrations.
+
+## Claude Code plugin
+
+Prefer a plugin over the manual setup above? Ratchet ships as a Claude Code
+plugin, with this repo doubling as its own marketplace:
+
+```text
+/plugin marketplace add krishansubudhi/ratchet
+/plugin install ratchet@ratchet
+```
+
+That installs a **Stop** hook (`ratchet check --hook`, falling back to `uvx`
+if `ratchet` isn't on `PATH` yet) so Claude Code can't end a turn with the
+repo over budget, plus a `/ratchet:setup` command that runs the
+[agent setup](SETUP-FOR-AGENTS.md) -- install, `ratchet init`, detect your
+harness, `ratchet check` -- in the repo you're in. See
+[`.claude-plugin/`](.claude-plugin) and [`hooks/hooks.json`](hooks/hooks.json)
+for the manifests, or `claude plugin validate .` to check them yourself.
+
+## What it counts
+
+**Scope:** the one git repository you run it in (`git rev-parse
+--show-toplevel`). Other repos on the machine are never touched, and each
+repo gets its own `.ratchet.json`.
+
+**Which files:** git-tracked files, plus untracked files that aren't
+gitignored, whose extension is one of the code extensions present at
+`init` (`.py`, `.js`, `.ts`, `.go`, `.rs`, `.java`, `.rb`, `.c`, `.sh`, and
+more -- see `CODE_EXTS` in `ratchet/measure.py`). Blank lines don't count.
+
+**Source vs tests:** a file matching a test glob (`test_*`, `*_test.*`,
+`*_tests.*`, `*.test.*`, `*.spec.*`, or living under `tests/`, `test/`,
+`__tests__/`, `spec/`) is `tests`; everything else is `source`. Both groups
+are plain config in `.ratchet.json` -- edit `include`/`exclude`/`extensions`
+to carve out a different split, e.g. `"exclude": ["vendor/**", "**/*.gen.*"]`
+to stop counting vendored or generated code.
+
+**Existing repo:** `ratchet init` measures today's totals and sets the
+ceilings there (plus optional `--slack`). A file already over
+`max_file_lines` is frozen at its current size, so nothing is refused on
+day one -- you start where you are. From then on a ceiling may only shrink,
+unless a human runs `ratchet grant`.
+
+## What the agent sees when refused
+
+```
+ratchet: REFUSED -- 2 problems (source 10,412/10,300, tests 4,980/5,000)
+
+1. source is 10,412 lines, ceiling 10,300: 112 over
+   grew vs HEAD: app/api.py +80, app/store.py +40
+   fix: remove at least 112 lines of source: delete dead code, reuse what
+   exists instead of adding a parallel version, simplify.
+2. app/api.py is 431 lines, limit 400
+   seams near the middle: line 198 `def upload`, line 230 `class Session`
+   fix: split it at a seam: move a cohesive group of definitions into a new
+   file, so each piece is under 400 lines.
+
+Do not edit .ratchet.json or .ratchet-grants.jsonl to get past this.
+If the growth is truly needed, stop and ask a human to run:
+  ratchet grant +112 --group source --reason "<why>" --by <name>
+  ratchet grant +31 --file app/api.py --reason "<why>" --by <name>
+```
+
+Every refusal says what grew, by how much, and which fix applies: shrink,
+split, or ask a human. For a harness, `ratchet check --json` gives the same
+result as data.
+
+## The four rules
+
+| Rule | What it does |
+|------|--------------|
+| **Budget** | Each group (`source`, `tests` by default) has a ceiling. A total over it is refused. |
+| **Seams** | A file over `max_file_lines` (default 400) is refused, with the top-level definitions nearest the middle offered as places to cut. A file already over the limit at `init` is recorded at its size: it may shrink, never grow. |
+| **Grants** | Only `ratchet grant` raises a limit, and every grant is appended to `.ratchet-grants.jsonl` with who and why. |
+| **Tighten** | `ratchet tighten` lowers every ceiling to the measured size (plus optional `slack`). Nothing ever raises it automatically. |
+
+Lines are counted without blanks. Docs, data, and fixtures don't count: only
+files whose extensions you list in `.ratchet.json` do.
+
+## How grants work
+
+Sometimes the growth is the point: a real feature, a new integration. Then a
+human runs:
+
+```sh
+ratchet grant +300 --group source --reason "CSV export (issue 41)" --by alice
+ratchet grant +60 --file app/api.py --reason "until the router split lands" --by alice
+```
+
+That raises the ceiling in `.ratchet.json` and appends a line to
+`.ratchet-grants.jsonl`:
+
+```json
+{"after": 10600, "before": 10300, "by": "alice", "lines": 300, "reason": "CSV export (issue 41)", "target": "source", "ts": "2026-01-15T09:30:00Z"}
+```
+
+Commit both files. Here is what keeps grants honest:
+
+- **In CI, run `ratchet check --base <target branch>`.** It refuses any ceiling
+  that is higher than the base's unless grants appended since the base pay for
+  it. An agent that edits `.ratchet.json` by hand passes locally and fails
+  review. The check also refuses a grants log that was rewritten rather than
+  appended to.
+- Grants are one-line diffs in the pull request, so a reviewer sees them.
+- Tell your agent never to run `ratchet grant`. The Claude Code integration
+  also puts it on the permission deny list.
+
+Run `ratchet tighten` after a cleanup and commit the result. The room you
+freed is now the new ceiling.
+
+## Running it by hand
+
+`ratchet check` exits `0` when the repo is within budget, `1` when refused,
+`2` on a setup error (bad config, not a git repo when `--base` is used, and
+so on). `python -m ratchet` works the same as the `ratchet` entry point, if
+you don't have it on `PATH`.
+
+## Integrations
+
+| Harness | How |
+|---------|-----|
+| Claude Code | Stop hook `ratchet check --hook`: [integrations/claude-code](integrations/claude-code/README.md) |
+| Cursor, Codex CLI, aider | instruction file + git hook / test-cmd: [integrations/other-agents.md](integrations/other-agents.md) |
+| pre-commit | framework hook, or a plain git hook: [integrations/pre-commit](integrations/pre-commit/README.md) |
+| GitHub Actions | `uses: krishansubudhi/ratchet@v0`: [integrations/github](integrations/github/README.md) |
+| Anything else | prompt snippet: [integrations/any-agent.md](integrations/any-agent.md) |
+
+## Configuration
+
+`ratchet init` writes `.ratchet.json`. It is JSON because ratchet must write
+the file, and Python's standard library reads TOML but cannot write it.
+
+```json
+{
+  "version": 1,
+  "max_file_lines": 400,
+  "slack": 0,
+  "groups": {
+    "source": {"include": ["**"], "exclude": ["**/tests/**", "**/test_*"], "extensions": [".py", ".ts"]},
+    "tests":  {"include": ["**/tests/**", "**/test_*"], "extensions": [".py", ".ts"]}
+  },
+  "ceilings": {"source": 10300, "tests": 5000},
+  "file_ceilings": {"app/legacy.py": 1210}
+}
+```
+
+- Globs work like gitignore: `**/` means any number of directories.
+- Each file belongs to the first group that matches it.
+- `slack` keeps some headroom above the measured size after `init` and
+  `tighten`, if you would rather not require a delete for every add.
+- Files are listed with `git ls-files`, so ignored files never count.
+  Outside git, ratchet walks the tree and skips the usual build and vendor
+  directories.
+
+`ratchet init --max-file-lines 300 --slack 50` sets both at creation.
+
+## Requirements
+
+Python 3.10+, git (optional, needed for `--base` and the "grew vs" lines). No
+dependencies. Tests: `pip install pytest && python -m pytest -q`.
+
+## License
+
+Apache-2.0. Copyright 2026 Krishan Subudhi.

ratchet_size-0.1.0/pyproject.toml

@@ -0,0 +1,34 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ratchet-size"
+version = "0.1.0"
+description = "A code-size budget that only goes down: keeps coding agents from bloating your repo."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+authors = [{name = "Krishan Subudhi"}]
+dependencies = []
+classifiers = [
+  "Programming Language :: Python :: 3",
+  "Topic :: Software Development :: Quality Assurance",
+]
+
+[project.urls]
+Homepage = "https://github.com/krishansubudhi/ratchet"
+Repository = "https://github.com/krishansubudhi/ratchet"
+Issues = "https://github.com/krishansubudhi/ratchet/issues"
+
+[project.optional-dependencies]
+test = ["pytest"]
+
+[project.scripts]
+ratchet = "ratchet.cli:main"
+
+[tool.setuptools]
+packages = ["ratchet"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

ratchet_size-0.1.0/ratchet/__init__.py

@@ -0,0 +1,5 @@
+# Copyright 2026 Krishan Subudhi
+# SPDX-License-Identifier: Apache-2.0
+"""ratchet: a code-size budget for repositories that coding agents work in."""
+
+__version__ = "0.1.0"

ratchet_size-0.1.0/ratchet/__main__.py

@@ -0,0 +1,7 @@
+# Copyright 2026 Krishan Subudhi
+# SPDX-License-Identifier: Apache-2.0
+import sys
+
+from .cli import main
+
+sys.exit(main())