namelint 0.1.0__tar.gz

namelint-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+corpus/
+.venv/
+__pycache__/
+*.egg-info/
+.ruff_cache/
+.pytest_cache/
+dist/
+build/

namelint-0.1.0/CHANGES.md

@@ -0,0 +1,21 @@
+# Changelog
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-10-02
+
+First release, to claim the name. Pre-release in substance: three of the eight specified checks, one of them on probation.
+
+### Added
+
+- `NAM101`: a function in a test module that asserts, takes no arguments, and is not named `test*`, so pytest never collects it.
+- `NAM106`: a `get_` whose body reaches a disk, a socket, a subprocess or a database.
+- `NAM107`: a generator whose name reads as if it returned a container.
+- The `namelint` CLI: `--select`, `--ignore`, `--json`, `--stats`, `--version`. Exit 0 clean, 1 findings, 2 the tool itself failed.
+- `tools/calibrate.py`: fetches the nine-project golden corpus and measures every check against it, writing a summary table, every finding as JSONL, and a seeded sample to adjudicate by hand.
+
+### Known
+
+- `NAM107` fires at 15.9 per thousand functions in `httpx` and 13.7 in `rich`, which is a rule in question rather than a result about those codebases. The false-positive class is the undecorated protocol generator.
+- No configuration file and no suppression mechanism yet; both wait on corpus evidence about what needs suppressing.

namelint-0.1.0/LICENSE

@@ -0,0 +1,215 @@
+                                 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.
+
+   Copyright 2026 Abilian SAS
+
+   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.

namelint-0.1.0/Makefile

@@ -0,0 +1,35 @@
+.PHONY: all test build format check lint clean
+
+all: test lint
+
+check: lint
+
+lint:
+	uv run --active ruff check
+	uv run --active ruff format --check
+	uv run --active ty check src
+	uv run --active pyrefly check src
+	uv run --active mypy src
+	# uv run --active mypy --strict src
+
+format:
+	uv run --active ruff format src tests
+	uv run --active ruff check src tests --fix
+	uv run --active ruff format src tests
+
+test:
+	uv run pytest
+
+test-cov:
+	uv run pytest --cov=namelint --cov-report=html --cov-report=term tests
+
+clean:
+	rm -rf .pytest_cache .ruff_cache dist build __pycache__ .mypy_cache \
+		.coverage htmlcov .coverage.* *.egg-info
+	-adt clean
+
+build: clean
+	uv build
+
+publish: build
+	uv publish

namelint-0.1.0/PKG-INFO

@@ -0,0 +1,181 @@
+Metadata-Version: 2.5
+Name: namelint
+Version: 0.1.0
+Summary: Reports where a Python function's name contradicts its body.
+Project-URL: Homepage, https://github.com/abilian/namelinter
+Project-URL: Repository, https://github.com/abilian/namelinter
+Project-URL: Issues, https://github.com/abilian/namelinter/issues
+Project-URL: Changelog, https://github.com/abilian/namelinter/blob/main/CHANGES.md
+Author: Abilian SAS
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ast,linter,naming,static-analysis
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# namelint
+
+Reports where a Python function's **name contradicts its body**.
+
+`ruff` already knows that `getUserName` is not `snake_case`. Nothing knows that `get_user` opens a socket, that `cleanup_files` is a generator nobody will iterate twice, or that `check_user_is_valid` sits in a test module asserting things pytest will never collect. That gap is what this tool is for: every check needs the AST, and none of them is a grep over identifiers.
+
+It holds **no opinion about vocabulary**. "Too generic", "too long", "prefer a domain term" belong in a style guide and a code review. namelint only reports that a name and the code under it disagree, and it names the fact that made it disagree, so you can argue with that fact rather than with the rule.
+
+## Install
+
+```sh
+uv tool install namelint     # on PATH, globally
+uvx namelint src/            # or without installing anything
+pip install namelint
+```
+
+No runtime dependencies, and that is a constraint rather than an accident: a linter you hesitate to add to a project because of what it drags in is a linter that does not get added. Python 3.12 or newer.
+
+## Use
+
+```sh
+namelint src/                          # lint a tree
+namelint src/app/users.py              # or one file
+namelint --select NAM106 src/          # one check only (repeatable)
+namelint --ignore NAM107 src/          # everything but one (repeatable)
+namelint --json src/                   # one JSON object per line
+namelint --stats src/                  # counts per check, with a rate
+```
+
+Output is the one line every editor and CI annotator already parses:
+
+```
+src/app/users.py:42:5: NAM106 get_user performs I/O (calls httpx.get); get_ promises a cheap lookup, use fetch_, load_ or read_
+```
+
+Exit codes: **0** clean, **1** findings, **2** namelint itself failed. A file it cannot parse is reported on stderr and skipped — one Python 2 file in a vendored tree must not end a run over 80,000 functions.
+
+`--stats` exists for calibration rather than for daily use, and reports per thousand functions so that two codebases of different sizes can be compared:
+
+```
+$ namelint --stats ~/src/cpython/Lib
+functions scanned: 61820
+  NAM101      28     0.45 per 1000
+  NAM106      26     0.42 per 1000
+  NAM107     115     1.86 per 1000
+```
+
+## The checks
+
+Three of the eight specified checks are implemented. Each is listed with what it reports **and what it deliberately stays quiet about**, because for this kind of rule the exemptions are most of the work.
+
+### `NAM101` — a test that will never run
+
+A function in a test module that contains an assertion, takes no arguments, and is not named `test*`. pytest collects `test*` and nothing else, so this function reports nothing, and a suite that stays green over it is telling you nothing about the code it claims to cover.
+
+```python
+# tests/test_users.py
+def check_user_is_valid():  # NAM101 — pytest will not collect this
+    assert build().ok
+```
+
+Silent on: anything under `src/` (a test module is a `test_*.py`, a `*_test.py`, or any file under a `tests/` directory); a decorated function, which is what a fixture looks like; a `_`-prefixed helper, since a leading underscore says "not collected" as plainly as a name can; and a helper that takes the thing it checks — `assert_ok(response)` is a helper, and arity is the discriminator. A `with pytest.raises(...)` counts as an assertion.
+
+### `NAM106` — a `get_` that performs I/O
+
+`get` is a contract in Python rather than a lazy choice: `dict.get`, `getattr`, `os.environ.get` are all cheap and total. A `get_` that opens a socket breaks the promise its caller read.
+
+```python
+def get_user(uid):  # NAM106 — calls httpx.get
+    return httpx.get(f"/u/{uid}").json()
+```
+
+Reported on `open`, `Path.read_*`/`write_*`, `urlopen`, DBAPI `execute`/`fetchone`/`fetchall`, socket `recv`/`send`, and anything rooted at `requests`, `httpx`, `urllib`, `socket`, `subprocess` or `aiohttp`. The suggestion is `fetch_`, `load_` or `read_`. `dict.get` and `getattr` are never the evidence.
+
+### `NAM107` — a generator under a non-lazy name
+
+A caller who believes they hold a list and actually hold a one-shot iterator writes a bug that surfaces two loops later, far from this function.
+
+```python
+def collect_stale_entry(root):  # NAM107 — contains yield
+    for path in root.iterdir():
+        if stale(path):
+            yield path
+```
+
+Silent on: a plural final word (`items`, `values`, `user_records`); a lazy prefix (`iter_`, `walk_`, `gen_`, `generate_`, `stream_`, `scan_`, `traverse_`, `produce_`, `yield_`, `enumerate_`, `chunk_`), checked after any leading underscores; dunders; and a `yield` that is a *protocol* rather than iteration — a pytest fixture, a `@contextmanager`, an `@asynccontextmanager`, a pluggy `@hookimpl` wrapper. In all four the noun name is correct on purpose (`db_session`, `temp_config`, `client`).
+
+**This check is the one currently in question.** It fires at 15.9 per thousand functions in `httpx` and 13.7 in `rich`, which is far outside what a well-named codebase should produce, and the known false-positive class is the undecorated protocol generator: an ABC method where `yield request` *is* the interface. Expect it to get a narrower detector or to drop to advisory before 1.0.
+
+### Still to come
+
+`NAM102` a `@property` whose name opens with a verb · `NAM103` an `is_`/`has_`/`can_` that does not return a bool · `NAM104` a bool return under a non-predicate name · `NAM105` a query-shaped name that returns `None` on every path · `NAM108` a method repeating its class name. The three that depend on reading return types share machinery and are being built together; `NAM108` is last because it is the one most likely to be cut.
+
+## Calibration
+
+A rule firing often on a codebase nobody thinks is badly named is a **wrong rule**, and it is no evidence at all about that codebase. So every check is measured against a fixed corpus of nine projects before it is allowed to ship, and a check running above roughly two false positives in thirty gets a narrower detector, drops to advisory, or is cut.
+
+```sh
+uv run tools/calibrate.py                 # fetch what is missing, then measure
+uv run tools/calibrate.py --only click    # one project
+uv run tools/calibrate.py --no-fetch      # re-measure after changing a detector
+```
+
+It shallow-clones CPython's `Lib/`, attrs, pydantic, requests, httpx, rich, click, pytest and flask into `corpus/`, then writes `calibration/summary.md` (the table), `findings.jsonl` (every finding, so two runs can be diffed) and `sample.md` (a seeded random sample per check, with source lines, as checkboxes to adjudicate by hand). The sample is seeded deliberately: measuring a changed detector against a fresh sample measures the sample. Every row records the commit it came from, because a number with no commit behind it is a rumour.
+
+The current run — 85,368 functions, 308 findings:
+
+| Project | NAM101 | NAM106 | NAM107 |
+|---|---:|---:|---:|
+| cpython `Lib/` | 0.45 | 0.42 | 1.86 |
+| attrs | 0.00 | 0.00 | 0.87 |
+| pydantic | 0.79 | 0.56 | 0.68 |
+| requests | 0.00 | 0.00 | 0.00 |
+| httpx | 0.00 | 0.88 | **15.87** |
+| rich | 0.55 | 0.00 | **13.71** |
+| click | 0.00 | 0.00 | **7.43** |
+| pytest | 0.46 | 0.46 | **7.97** |
+| flask | 0.00 | 1.37 | 0.68 |
+
+Findings per thousand functions. CPython is pinned to `v3.13.0`, since `main` uses syntax a 3.14 interpreter cannot parse and measuring it would measure the interpreter instead of the corpus.
+
+## As a library
+
+`check_module(tree, path) -> list[Finding]` is also flake8's plugin contract, so a flake8 adapter is an entry point and a wrapper rather than a second implementation. `checks.py` imports nothing but `ast` and two frozen records, and is a pure function of a node and a `Context` — no filesystem, no configuration.
+
+```python
+import ast
+from pathlib import Path
+from namelint.visitor import check_module, check_source
+
+for finding in check_source(
+    "def get_user(u):\n    return httpx.get(u)\n", Path("x.py")
+):
+    print(finding.code, finding.name, finding.evidence)
+```
+
+Every `Finding` carries `code`, `line`, `col`, `name`, `message` and `evidence`. `evidence` names the fact that produced the finding: "calls `httpx.get`" is arguable, "performs I/O" is not.
+
+There is no ruff plugin because ruff has no plugin API.
+
+## Status
+
+**0.1.0, pre-release.** Three checks of eight, one of which is on probation. The output format and the `NAM1xx` codes are not frozen yet. There is no configuration file and no suppression mechanism; both are waiting on evidence from the corpus about what actually needs suppressing — `requests`, where `get` is the HTTP verb, already shows that the first exception needed is module-scoped.
+
+## Development
+
+```sh
+uv sync
+make test          # pytest
+make lint          # ruff check, ruff format --check, ty, pyrefly, mypy
+nox -s tests       # against 3.12, 3.13 and 3.14
+```
+
+Reasoning behind each rule, the corpus design and the open questions: `notes/02-specs.md`. Where the rules came from, and what was rejected: `notes/01-background.md`.
+
+A new check is not finished when it passes its tests. It is finished when it has been run over the corpus and adjudicated, and the sample is in the commit.
+
+## Licence
+
+Apache 2.0. Copyright 2026 Abilian SAS.

namelint-0.1.0/README.md

@@ -0,0 +1,160 @@
+# namelint
+
+Reports where a Python function's **name contradicts its body**.
+
+`ruff` already knows that `getUserName` is not `snake_case`. Nothing knows that `get_user` opens a socket, that `cleanup_files` is a generator nobody will iterate twice, or that `check_user_is_valid` sits in a test module asserting things pytest will never collect. That gap is what this tool is for: every check needs the AST, and none of them is a grep over identifiers.
+
+It holds **no opinion about vocabulary**. "Too generic", "too long", "prefer a domain term" belong in a style guide and a code review. namelint only reports that a name and the code under it disagree, and it names the fact that made it disagree, so you can argue with that fact rather than with the rule.
+
+## Install
+
+```sh
+uv tool install namelint     # on PATH, globally
+uvx namelint src/            # or without installing anything
+pip install namelint
+```
+
+No runtime dependencies, and that is a constraint rather than an accident: a linter you hesitate to add to a project because of what it drags in is a linter that does not get added. Python 3.12 or newer.
+
+## Use
+
+```sh
+namelint src/                          # lint a tree
+namelint src/app/users.py              # or one file
+namelint --select NAM106 src/          # one check only (repeatable)
+namelint --ignore NAM107 src/          # everything but one (repeatable)
+namelint --json src/                   # one JSON object per line
+namelint --stats src/                  # counts per check, with a rate
+```
+
+Output is the one line every editor and CI annotator already parses:
+
+```
+src/app/users.py:42:5: NAM106 get_user performs I/O (calls httpx.get); get_ promises a cheap lookup, use fetch_, load_ or read_
+```
+
+Exit codes: **0** clean, **1** findings, **2** namelint itself failed. A file it cannot parse is reported on stderr and skipped — one Python 2 file in a vendored tree must not end a run over 80,000 functions.
+
+`--stats` exists for calibration rather than for daily use, and reports per thousand functions so that two codebases of different sizes can be compared:
+
+```
+$ namelint --stats ~/src/cpython/Lib
+functions scanned: 61820
+  NAM101      28     0.45 per 1000
+  NAM106      26     0.42 per 1000
+  NAM107     115     1.86 per 1000
+```
+
+## The checks
+
+Three of the eight specified checks are implemented. Each is listed with what it reports **and what it deliberately stays quiet about**, because for this kind of rule the exemptions are most of the work.
+
+### `NAM101` — a test that will never run
+
+A function in a test module that contains an assertion, takes no arguments, and is not named `test*`. pytest collects `test*` and nothing else, so this function reports nothing, and a suite that stays green over it is telling you nothing about the code it claims to cover.
+
+```python
+# tests/test_users.py
+def check_user_is_valid():  # NAM101 — pytest will not collect this
+    assert build().ok
+```
+
+Silent on: anything under `src/` (a test module is a `test_*.py`, a `*_test.py`, or any file under a `tests/` directory); a decorated function, which is what a fixture looks like; a `_`-prefixed helper, since a leading underscore says "not collected" as plainly as a name can; and a helper that takes the thing it checks — `assert_ok(response)` is a helper, and arity is the discriminator. A `with pytest.raises(...)` counts as an assertion.
+
+### `NAM106` — a `get_` that performs I/O
+
+`get` is a contract in Python rather than a lazy choice: `dict.get`, `getattr`, `os.environ.get` are all cheap and total. A `get_` that opens a socket breaks the promise its caller read.
+
+```python
+def get_user(uid):  # NAM106 — calls httpx.get
+    return httpx.get(f"/u/{uid}").json()
+```
+
+Reported on `open`, `Path.read_*`/`write_*`, `urlopen`, DBAPI `execute`/`fetchone`/`fetchall`, socket `recv`/`send`, and anything rooted at `requests`, `httpx`, `urllib`, `socket`, `subprocess` or `aiohttp`. The suggestion is `fetch_`, `load_` or `read_`. `dict.get` and `getattr` are never the evidence.
+
+### `NAM107` — a generator under a non-lazy name
+
+A caller who believes they hold a list and actually hold a one-shot iterator writes a bug that surfaces two loops later, far from this function.
+
+```python
+def collect_stale_entry(root):  # NAM107 — contains yield
+    for path in root.iterdir():
+        if stale(path):
+            yield path
+```
+
+Silent on: a plural final word (`items`, `values`, `user_records`); a lazy prefix (`iter_`, `walk_`, `gen_`, `generate_`, `stream_`, `scan_`, `traverse_`, `produce_`, `yield_`, `enumerate_`, `chunk_`), checked after any leading underscores; dunders; and a `yield` that is a *protocol* rather than iteration — a pytest fixture, a `@contextmanager`, an `@asynccontextmanager`, a pluggy `@hookimpl` wrapper. In all four the noun name is correct on purpose (`db_session`, `temp_config`, `client`).
+
+**This check is the one currently in question.** It fires at 15.9 per thousand functions in `httpx` and 13.7 in `rich`, which is far outside what a well-named codebase should produce, and the known false-positive class is the undecorated protocol generator: an ABC method where `yield request` *is* the interface. Expect it to get a narrower detector or to drop to advisory before 1.0.
+
+### Still to come
+
+`NAM102` a `@property` whose name opens with a verb · `NAM103` an `is_`/`has_`/`can_` that does not return a bool · `NAM104` a bool return under a non-predicate name · `NAM105` a query-shaped name that returns `None` on every path · `NAM108` a method repeating its class name. The three that depend on reading return types share machinery and are being built together; `NAM108` is last because it is the one most likely to be cut.
+
+## Calibration
+
+A rule firing often on a codebase nobody thinks is badly named is a **wrong rule**, and it is no evidence at all about that codebase. So every check is measured against a fixed corpus of nine projects before it is allowed to ship, and a check running above roughly two false positives in thirty gets a narrower detector, drops to advisory, or is cut.
+
+```sh
+uv run tools/calibrate.py                 # fetch what is missing, then measure
+uv run tools/calibrate.py --only click    # one project
+uv run tools/calibrate.py --no-fetch      # re-measure after changing a detector
+```
+
+It shallow-clones CPython's `Lib/`, attrs, pydantic, requests, httpx, rich, click, pytest and flask into `corpus/`, then writes `calibration/summary.md` (the table), `findings.jsonl` (every finding, so two runs can be diffed) and `sample.md` (a seeded random sample per check, with source lines, as checkboxes to adjudicate by hand). The sample is seeded deliberately: measuring a changed detector against a fresh sample measures the sample. Every row records the commit it came from, because a number with no commit behind it is a rumour.
+
+The current run — 85,368 functions, 308 findings:
+
+| Project | NAM101 | NAM106 | NAM107 |
+|---|---:|---:|---:|
+| cpython `Lib/` | 0.45 | 0.42 | 1.86 |
+| attrs | 0.00 | 0.00 | 0.87 |
+| pydantic | 0.79 | 0.56 | 0.68 |
+| requests | 0.00 | 0.00 | 0.00 |
+| httpx | 0.00 | 0.88 | **15.87** |
+| rich | 0.55 | 0.00 | **13.71** |
+| click | 0.00 | 0.00 | **7.43** |
+| pytest | 0.46 | 0.46 | **7.97** |
+| flask | 0.00 | 1.37 | 0.68 |
+
+Findings per thousand functions. CPython is pinned to `v3.13.0`, since `main` uses syntax a 3.14 interpreter cannot parse and measuring it would measure the interpreter instead of the corpus.
+
+## As a library
+
+`check_module(tree, path) -> list[Finding]` is also flake8's plugin contract, so a flake8 adapter is an entry point and a wrapper rather than a second implementation. `checks.py` imports nothing but `ast` and two frozen records, and is a pure function of a node and a `Context` — no filesystem, no configuration.
+
+```python
+import ast
+from pathlib import Path
+from namelint.visitor import check_module, check_source
+
+for finding in check_source(
+    "def get_user(u):\n    return httpx.get(u)\n", Path("x.py")
+):
+    print(finding.code, finding.name, finding.evidence)
+```
+
+Every `Finding` carries `code`, `line`, `col`, `name`, `message` and `evidence`. `evidence` names the fact that produced the finding: "calls `httpx.get`" is arguable, "performs I/O" is not.
+
+There is no ruff plugin because ruff has no plugin API.
+
+## Status
+
+**0.1.0, pre-release.** Three checks of eight, one of which is on probation. The output format and the `NAM1xx` codes are not frozen yet. There is no configuration file and no suppression mechanism; both are waiting on evidence from the corpus about what actually needs suppressing — `requests`, where `get` is the HTTP verb, already shows that the first exception needed is module-scoped.
+
+## Development
+
+```sh
+uv sync
+make test          # pytest
+make lint          # ruff check, ruff format --check, ty, pyrefly, mypy
+nox -s tests       # against 3.12, 3.13 and 3.14
+```
+
+Reasoning behind each rule, the corpus design and the open questions: `notes/02-specs.md`. Where the rules came from, and what was rejected: `notes/01-background.md`.
+
+A new check is not finished when it passes its tests. It is finished when it has been run over the corpus and adjudicated, and the sample is in the commit.
+
+## Licence
+
+Apache 2.0. Copyright 2026 Abilian SAS.