penlike 0.0.2__tar.gz

penlike-0.0.2/.github/workflows/ci.yml

@@ -0,0 +1,43 @@
+# wads CI — calls the reusable workflow hosted in i2mint/wads.
+#
+# All configuration comes from this repo's pyproject.toml [tool.wads.ci.*].
+# To customize the workflow itself (rare), replace this file with the
+# full inline template `wads/data/github_ci_uv.yml` from i2mint/wads.
+#
+# Pinning: `@master` floats with wads. If you need version stability for
+# a release-sensitive repo, change `@master` to a wads tag (e.g. `@0.2.15`;
+# tags have no `v` prefix). A stub whose `secrets:` block passes the JSON
+# transport (the default below) needs a tag from a release after 0.2.14 —
+# older tags don't declare that secret and GitHub then rejects the
+# workflow at parse time.
+# CI failure does not block a published release — it blocks the publish
+# step itself — so floating master is generally safe.
+#
+# Permissions: GitHub validates that the caller grants AT LEAST the
+# permissions any job in the called workflow requests — at workflow-parse
+# time, not at run-time, even if the job would be skipped via `if:`.
+# The reusable workflow needs:
+#   contents: write   for the publish job's version-bump push-back
+#                     and for the github-pages job's gh-pages branch push
+#   pages: write      for the github-pages job's REST API Pages config
+# Both default to `write` on org-account GITHUB_TOKEN and need to be
+# granted explicitly on personal-account callers (where the default is
+# read-only). No `id-token: write` needed — the publish-github-pages
+# action uses peaceiris/actions-gh-pages (branch-based) + REST API,
+# not the OIDC `actions/deploy-pages` flow.
+name: Continuous Integration
+on: [push, pull_request]
+jobs:
+  ci:
+    uses: i2mint/wads/.github/workflows/uv-ci.yml@master
+    permissions:
+      contents: write
+      pages: write
+    # Transport (NAMED, legacy): explicitly passes only the secrets
+    # listed below (PYPI_PASSWORD + those declared in
+    # [tool.wads.ci.env]). Every name must be in the frozen wads
+    # superset (wads/ci_secrets.py) or GitHub rejects the workflow
+    # at parse time. The default JSON transport has no such limit;
+    # regenerate with `wads-migrate ci-to-stub` to switch.
+    secrets:
+      PYPI_PASSWORD: ${{ secrets.PYPI_PASSWORD }}

penlike-0.0.2/.gitignore

@@ -0,0 +1,120 @@
+.claude/handoffs/
+.claude/scratch/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+
+.DS_Store
+# C extensions
+*.so
+
+# TLS certificates
+## Ignore all PEM files anywhere
+*.pem
+## Also ignore any certs directory
+certs/
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+_build
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+docs/*
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+
+# PyCharm
+.idea

penlike-0.0.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Thor Whalen
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

penlike-0.0.2/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.5
+Name: penlike
+Version: 0.0.2
+Summary: Model how an author, a group or a corpus writes, register by register, and give agents the skills to write in that style
+Project-URL: Homepage, https://github.com/thorwhalen/penlike
+Project-URL: Repository, https://github.com/thorwhalen/penlike
+Project-URL: Documentation, https://thorwhalen.github.io/penlike
+Author: Thor Whalen
+License: MIT
+License-File: LICENSE
+Keywords: agent-skills,authorship,idiolect,llm,register,style-transfer,stylometry,writing,writing-style
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Text Processing :: Linguistic
+Requires-Python: >=3.10
+Requires-Dist: cw<0.2,>=0.1.1
+Requires-Dist: dol
+Provides-Extra: correspond
+Requires-Dist: correspond; extra == 'correspond'
+Provides-Extra: dev
+Requires-Dist: pytest-cov>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Requires-Dist: ruff>=0.1.0; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: sphinx-rtd-theme>=1.0; extra == 'docs'
+Requires-Dist: sphinx>=6.0; extra == 'docs'
+Provides-Extra: mcp
+Requires-Dist: py2mcp>=0.1.12; extra == 'mcp'
+Provides-Extra: screen
+Requires-Dist: ductus; extra == 'screen'
+Description-Content-Type: text/markdown
+
+# penlike
+
+Model how an author writes, register by register, and give an agent what it needs to write in that style. The author can be one person (by default: you), a group, or any corpus.
+
+```bash
+pip install penlike
+```
+
+```bash
+penlike new me --me you@example.org
+penlike gather me mbox ~/mail/sent.mbox --until 2023-01-01
+penlike build me
+penlike brief --like me --channel email --to ada@example.org   # what to read before writing
+penlike check draft.md --like me --style email.one             # what in the draft is not like you
+```
+
+penlike is made to be used by an agent. Its main surface is three skills:
+
+```bash
+gh skill install thorwhalen/penlike penlike --agent claude-code
+gh skill install thorwhalen/penlike penlike-model --agent claude-code
+gh skill install thorwhalen/penlike penlike-source --agent claude-code
+```
+
+or, from the installed package, with no network: `penlike install-skills --write`.
+
+| Skill | Use it to |
+|---|---|
+| `penlike` | write or rewrite a text in an author's style ("write like me", "in my technical register") |
+| `penlike-model` | build a model, name its registers, add notes, keep it current |
+| `penlike-source` | choose and read the texts, write a custom sourcer, screen for machine-written text |
+
+`gh skill` needs a recent GitHub CLI.
+
+## What a model is
+
+A person does not have one style. They write one way to a close colleague, another to a whole team, another in a technical discussion. penlike calls each of these a **register** and models each one separately.
+
+A model holds:
+
+- the author's **texts**, each filed under a register;
+- a **measured profile** of each register: sentence and word lengths, punctuation, contractions, function words, greetings and sign-offs, formatting habits, word sequences the author returns to;
+- what sets each register apart from the author's others;
+- **notes** on what numbers miss, each with the texts it rests on;
+- a way to pick **examples**.
+
+When asked to write, `penlike brief` picks the register that fits the situation, and returns its profile, notes and examples. `penlike check` measures a draft against the same register and lists what differs, with figures.
+
+## Your texts stay private
+
+A model of how you write is private data, and so is everything in it. It is stored under `~/.local/share/penlike` (set `PENLIKE_DATA_DIR` to move it), never in a project folder. Do not commit a model, a profile, or texts it was built from to a repository.
+
+## Use texts written before 2023
+
+Since late 2022 a growing share of what people send has been drafted or polished by a language model. A model of you built from such text learns the machine's habits as yours. The simplest protection is a date:
+
+```bash
+penlike gather me github your-login --until 2023-01-01
+```
+
+The trade-off is age: older text is cleaner and may be less like how you write now. Whatever you choose, `gather` tells you how many of the texts it kept are dated in the era of language models.
+
+## Sources
+
+```bash
+penlike sources
+```
+
+| Sourcer | Reads |
+|---|---|
+| `mbox` | a mailbox archive, such as a webmail export |
+| `github` | what one login wrote: discussions, issues, pull requests and the comments on them, not line-by-line review comments (through the `gh` tool) |
+| `correspond` | any channel of the [correspond](https://github.com/thorwhalen/correspond) package (`pip install 'penlike[correspond]'`) |
+| `files` | text files, folders of them, `.eml` messages |
+| `jsonl` | one JSON document per line |
+| `claude-sessions` | what you typed to a coding agent, which is rarely how you write to people |
+
+When none fits, a sourcer is a plain function that yields dicts, referenced by where it lives:
+
+```python
+def read(*refs, since=None, until=None, limit=None, me=(), **options):
+    for path in refs:
+        ...
+        yield {"text": body, "date": sent, "channel": "chat", "to": readers, "is_self": True}
+```
+
+```bash
+penlike gather me ~/.config/penlike/sourcers/chat.py:read ~/exports/chat.json
+```
+
+Only `text` is required. `to` and `channel` decide the register, `date` allows a cutoff, `is_self` keeps other people's writing out. Quoted replies and forwarded messages are removed from every text by rules over plain text, which can miss an unusual mail program: read a sample of what was gathered (`penlike docs me --full`). The `penlike-source` skill tells an agent how to write one for you.
+
+## Registers
+
+Texts are filed by **situation** first: email by number of readers (`email.one`, `email.few`, `email.many`), GitHub writing by opening or reply, and so on. Then penlike looks inside each for groups written differently, and proposes them:
+
+```bash
+penlike propose me
+penlike register-add me close-colleagues --proposal email.one#2
+```
+
+A proposal is a question: you name the register, or decline. A named register keeps its identifier for good, and later texts join it when they are close enough. Routing, when you ask to write:
+
+| You give | Register chosen |
+|---|---|
+| `--style close-colleagues` | the one you named |
+| `--to ada@example.org` | the one you have used most with that reader |
+| `--channel email --audience many` | the one for that situation |
+| nothing | the largest, and the brief says it is a guess |
+
+## One person, a group, a corpus
+
+```bash
+penlike new me
+penlike new house-style --kind group --basis consent
+penlike new field-guide --kind corpus --basis public
+```
+
+| Kind | Kept | Specific to it |
+|---|---|---|
+| `person` | only the author's own texts | registers by reader, greetings and sign-offs, how they write to each person |
+| `group` | everyone's texts | shared conventions; individual habits average out |
+| `corpus` | everything | text types; readers and dates are often unknown |
+
+Measuring and checking are the same in all three. What differs is what is kept, how texts are filed, and what may be claimed.
+
+## Screening for machine-written text (optional)
+
+```bash
+penlike screen me --tier cheap          # says what it would cost; changes nothing
+penlike screen me --tier cheap --run
+```
+
+| Tier | What it does | Cost |
+|---|---|---|
+| `date` | excludes texts dated on or after a cutoff | none |
+| `cheap` | wording, mechanics, sentence shapes, rhythm (`pip install 'penlike[screen]'`) | no model, no network; milliseconds a text |
+| `heavy` | adds detectors that run small language models on your machine (`pip install 'ductus[local]'`) | processor time, timed on a sample first; a model download on first use |
+| `agent` | an agent reads each text | model tokens, in proportion to the corpus |
+
+Without `--run`, nothing is changed and the cost is stated. Flagged texts are excluded, never deleted: `penlike exclude me <id> --undo` puts one back. No detector is reliable on one short text, and each accuses some human writing. The date is the tier to trust. Screening uses [ductus](https://github.com/thorwhalen/ductus).
+
+## Writing to someone, in your voice
+
+penlike answers "how does the author write?". [acquaint](https://github.com/thorwhalen/acquaint) answers a different question: "what does this reader need?". To write to a known person in your own voice, use both: penlike for the voice, acquaint for the reader. The `penlike` skill does this when acquaint is installed.
+
+## From Python
+
+```python
+import penlike
+
+penlike.new("me", me=["you@example.org"])
+penlike.gather("me", "mbox", ["sent.mbox"], until="2023-01-01")
+penlike.build("me")
+brief = penlike.brief(like="me", channel="email", to=["ada@example.org"])
+print(brief["text"])
+report = penlike.check(draft, like="me", style=brief["register"])
+for item in report["discrepancies"]:
+    print(item["message"])
+```
+
+Every verb returns a JSON-ready dict with `ok`, a `summary` and usually a `text`. The same verbs are served over MCP by `penlike-mcp` (`pip install 'penlike[mcp]'`), except those that reach into the machine: gathering, deleting a model, writing batch files and linking skills stay at the terminal.
+
+## Limits
+
+- Passing `check` means the measurable surface of a draft matches the author. It does not mean a reader who knows them would take the text for theirs.
+- Imitation by a language model works best on structured writing and worst on informal, personal writing.
+- A register with under about 2000 words is marked provisional; its figures are rough.
+- The word lists (function words, hedges, greetings) are English. On other languages the lengths, punctuation and formatting features still hold.
+- The thresholds used to propose registers were set on synthetic text. Treat proposals as questions.
+
+## Responsible use
+
+Build a model of your own writing, or of an author who agreed to it. Do not present a text as written by someone who neither wrote nor approved it. Follow the usage policy of the language model you use. Every model records the basis on which it was made.
+
+## Research
+
+The design follows a review of the literature on stylometry, style imitation with language models, and register: [misc/docs/research_report.md](misc/docs/research_report.md). The design record is [misc/docs/design.md](misc/docs/design.md).

penlike-0.0.2/README.md

@@ -0,0 +1,178 @@
+# penlike
+
+Model how an author writes, register by register, and give an agent what it needs to write in that style. The author can be one person (by default: you), a group, or any corpus.
+
+```bash
+pip install penlike
+```
+
+```bash
+penlike new me --me you@example.org
+penlike gather me mbox ~/mail/sent.mbox --until 2023-01-01
+penlike build me
+penlike brief --like me --channel email --to ada@example.org   # what to read before writing
+penlike check draft.md --like me --style email.one             # what in the draft is not like you
+```
+
+penlike is made to be used by an agent. Its main surface is three skills:
+
+```bash
+gh skill install thorwhalen/penlike penlike --agent claude-code
+gh skill install thorwhalen/penlike penlike-model --agent claude-code
+gh skill install thorwhalen/penlike penlike-source --agent claude-code
+```
+
+or, from the installed package, with no network: `penlike install-skills --write`.
+
+| Skill | Use it to |
+|---|---|
+| `penlike` | write or rewrite a text in an author's style ("write like me", "in my technical register") |
+| `penlike-model` | build a model, name its registers, add notes, keep it current |
+| `penlike-source` | choose and read the texts, write a custom sourcer, screen for machine-written text |
+
+`gh skill` needs a recent GitHub CLI.
+
+## What a model is
+
+A person does not have one style. They write one way to a close colleague, another to a whole team, another in a technical discussion. penlike calls each of these a **register** and models each one separately.
+
+A model holds:
+
+- the author's **texts**, each filed under a register;
+- a **measured profile** of each register: sentence and word lengths, punctuation, contractions, function words, greetings and sign-offs, formatting habits, word sequences the author returns to;
+- what sets each register apart from the author's others;
+- **notes** on what numbers miss, each with the texts it rests on;
+- a way to pick **examples**.
+
+When asked to write, `penlike brief` picks the register that fits the situation, and returns its profile, notes and examples. `penlike check` measures a draft against the same register and lists what differs, with figures.
+
+## Your texts stay private
+
+A model of how you write is private data, and so is everything in it. It is stored under `~/.local/share/penlike` (set `PENLIKE_DATA_DIR` to move it), never in a project folder. Do not commit a model, a profile, or texts it was built from to a repository.
+
+## Use texts written before 2023
+
+Since late 2022 a growing share of what people send has been drafted or polished by a language model. A model of you built from such text learns the machine's habits as yours. The simplest protection is a date:
+
+```bash
+penlike gather me github your-login --until 2023-01-01
+```
+
+The trade-off is age: older text is cleaner and may be less like how you write now. Whatever you choose, `gather` tells you how many of the texts it kept are dated in the era of language models.
+
+## Sources
+
+```bash
+penlike sources
+```
+
+| Sourcer | Reads |
+|---|---|
+| `mbox` | a mailbox archive, such as a webmail export |
+| `github` | what one login wrote: discussions, issues, pull requests and the comments on them, not line-by-line review comments (through the `gh` tool) |
+| `correspond` | any channel of the [correspond](https://github.com/thorwhalen/correspond) package (`pip install 'penlike[correspond]'`) |
+| `files` | text files, folders of them, `.eml` messages |
+| `jsonl` | one JSON document per line |
+| `claude-sessions` | what you typed to a coding agent, which is rarely how you write to people |
+
+When none fits, a sourcer is a plain function that yields dicts, referenced by where it lives:
+
+```python
+def read(*refs, since=None, until=None, limit=None, me=(), **options):
+    for path in refs:
+        ...
+        yield {"text": body, "date": sent, "channel": "chat", "to": readers, "is_self": True}
+```
+
+```bash
+penlike gather me ~/.config/penlike/sourcers/chat.py:read ~/exports/chat.json
+```
+
+Only `text` is required. `to` and `channel` decide the register, `date` allows a cutoff, `is_self` keeps other people's writing out. Quoted replies and forwarded messages are removed from every text by rules over plain text, which can miss an unusual mail program: read a sample of what was gathered (`penlike docs me --full`). The `penlike-source` skill tells an agent how to write one for you.
+
+## Registers
+
+Texts are filed by **situation** first: email by number of readers (`email.one`, `email.few`, `email.many`), GitHub writing by opening or reply, and so on. Then penlike looks inside each for groups written differently, and proposes them:
+
+```bash
+penlike propose me
+penlike register-add me close-colleagues --proposal email.one#2
+```
+
+A proposal is a question: you name the register, or decline. A named register keeps its identifier for good, and later texts join it when they are close enough. Routing, when you ask to write:
+
+| You give | Register chosen |
+|---|---|
+| `--style close-colleagues` | the one you named |
+| `--to ada@example.org` | the one you have used most with that reader |
+| `--channel email --audience many` | the one for that situation |
+| nothing | the largest, and the brief says it is a guess |
+
+## One person, a group, a corpus
+
+```bash
+penlike new me
+penlike new house-style --kind group --basis consent
+penlike new field-guide --kind corpus --basis public
+```
+
+| Kind | Kept | Specific to it |
+|---|---|---|
+| `person` | only the author's own texts | registers by reader, greetings and sign-offs, how they write to each person |
+| `group` | everyone's texts | shared conventions; individual habits average out |
+| `corpus` | everything | text types; readers and dates are often unknown |
+
+Measuring and checking are the same in all three. What differs is what is kept, how texts are filed, and what may be claimed.
+
+## Screening for machine-written text (optional)
+
+```bash
+penlike screen me --tier cheap          # says what it would cost; changes nothing
+penlike screen me --tier cheap --run
+```
+
+| Tier | What it does | Cost |
+|---|---|---|
+| `date` | excludes texts dated on or after a cutoff | none |
+| `cheap` | wording, mechanics, sentence shapes, rhythm (`pip install 'penlike[screen]'`) | no model, no network; milliseconds a text |
+| `heavy` | adds detectors that run small language models on your machine (`pip install 'ductus[local]'`) | processor time, timed on a sample first; a model download on first use |
+| `agent` | an agent reads each text | model tokens, in proportion to the corpus |
+
+Without `--run`, nothing is changed and the cost is stated. Flagged texts are excluded, never deleted: `penlike exclude me <id> --undo` puts one back. No detector is reliable on one short text, and each accuses some human writing. The date is the tier to trust. Screening uses [ductus](https://github.com/thorwhalen/ductus).
+
+## Writing to someone, in your voice
+
+penlike answers "how does the author write?". [acquaint](https://github.com/thorwhalen/acquaint) answers a different question: "what does this reader need?". To write to a known person in your own voice, use both: penlike for the voice, acquaint for the reader. The `penlike` skill does this when acquaint is installed.
+
+## From Python
+
+```python
+import penlike
+
+penlike.new("me", me=["you@example.org"])
+penlike.gather("me", "mbox", ["sent.mbox"], until="2023-01-01")
+penlike.build("me")
+brief = penlike.brief(like="me", channel="email", to=["ada@example.org"])
+print(brief["text"])
+report = penlike.check(draft, like="me", style=brief["register"])
+for item in report["discrepancies"]:
+    print(item["message"])
+```
+
+Every verb returns a JSON-ready dict with `ok`, a `summary` and usually a `text`. The same verbs are served over MCP by `penlike-mcp` (`pip install 'penlike[mcp]'`), except those that reach into the machine: gathering, deleting a model, writing batch files and linking skills stay at the terminal.
+
+## Limits
+
+- Passing `check` means the measurable surface of a draft matches the author. It does not mean a reader who knows them would take the text for theirs.
+- Imitation by a language model works best on structured writing and worst on informal, personal writing.
+- A register with under about 2000 words is marked provisional; its figures are rough.
+- The word lists (function words, hedges, greetings) are English. On other languages the lengths, punctuation and formatting features still hold.
+- The thresholds used to propose registers were set on synthetic text. Treat proposals as questions.
+
+## Responsible use
+
+Build a model of your own writing, or of an author who agreed to it. Do not present a text as written by someone who neither wrote nor approved it. Follow the usage policy of the language model you use. Every model records the basis on which it was made.
+
+## Research
+
+The design follows a review of the literature on stylometry, style imitation with language models, and register: [misc/docs/research_report.md](misc/docs/research_report.md). The design record is [misc/docs/design.md](misc/docs/design.md).

penlike-0.0.2/penlike/__init__.py

@@ -0,0 +1,88 @@
+"""Model how an author, a group or a corpus writes, and write in that style.
+
+penlike keeps a *model* of a writer: their texts, filed by register (the situation
+a text was written in), a measured profile of each register, notes on what numbers
+miss, and examples. An agent asks for a brief before writing and checks its draft
+afterwards.
+
+>>> import penlike
+>>> files = {}
+>>> _ = penlike.new("ada", files=files)
+>>> penlike.models(files=files)["summary"]
+'1 model(s)'
+
+Everything a model holds is private and lives under the user's data folder
+(``~/.local/share/penlike`` by default), never in a project.
+"""
+
+from penlike.base import AI_ERA_START, PenlikeError, normalize_doc
+from penlike.routing import situate
+from penlike.sourcers import SOURCERS, resolve_sourcer
+from penlike.store import ModelStore, data_dir
+from penlike.tools import (
+    TOOLS,
+    assign,
+    batches,
+    brief,
+    build,
+    check,
+    docs,
+    exclude,
+    exemplars,
+    gather,
+    install_skills,
+    measure,
+    models,
+    new,
+    note,
+    notes,
+    propose,
+    register_add,
+    register_edit,
+    register_merge,
+    registers,
+    remove,
+    route,
+    screen,
+    show,
+    sources,
+    use,
+)
+
+__all__ = [
+    "AI_ERA_START",
+    "SOURCERS",
+    "TOOLS",
+    "ModelStore",
+    "PenlikeError",
+    "assign",
+    "batches",
+    "brief",
+    "build",
+    "check",
+    "data_dir",
+    "docs",
+    "exclude",
+    "exemplars",
+    "gather",
+    "install_skills",
+    "measure",
+    "models",
+    "new",
+    "normalize_doc",
+    "note",
+    "notes",
+    "propose",
+    "register_add",
+    "register_edit",
+    "register_merge",
+    "registers",
+    "remove",
+    "resolve_sourcer",
+    "route",
+    "screen",
+    "show",
+    "situate",
+    "sources",
+    "use",
+]