jeles 0.1.0__tar.gz

jeles-0.1.0/.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

jeles-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,24 @@
+## Bite
+
+<!-- One sentence — the single outcome this PR delivers.
+     Follow-up to a merged PR? Say so: "Follow-up to #NN (merged)". -->
+
+## What was done
+
+<!-- Bullets, boldest fact first. If two unrelated changes rode this
+     branch, flag them separately so they can be reviewed (or split) cleanly. -->
+
+## Evidence
+
+<!-- Receipts, not claims. Check only what you actually ran, and state the result. -->
+- [ ] Tests: `<command>` → N passed
+- [ ] Gates: `<gate command>` → clean
+- [ ] Driven for real: <!-- what you exercised end-to-end, and what you saw -->
+
+## Out of scope
+
+<!-- What this deliberately does not do, and where that work lives. -->
+
+## Next bite
+
+<!-- The single next bite this opens, if any. -->

jeles-0.1.0/.github/workflows/dependabot-automerge.yml

@@ -0,0 +1,55 @@
+name: Dependabot auto-merge
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+  push:
+    branches: [master, main]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  dependabot-pr:
+    if: github.event_name == 'pull_request' && github.event.pull_request.user.login == 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Fetch Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v3
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Update branch with base
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PR_NUMBER: ${{ github.event.pull_request.number }}
+        run: gh pr update-branch "$PR_NUMBER" --repo "${{ github.repository }}"
+
+      - name: Enable auto-merge
+        if: |
+          steps.metadata.outputs.update-type == 'version-update:semver-patch' ||
+          steps.metadata.outputs.update-type == 'version-update:semver-minor' ||
+          steps.metadata.outputs.update-type == 'version-update:semver-major' ||
+          steps.metadata.outputs.update-type == 'github_actions'
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PR_URL: ${{ github.event.pull_request.html_url }}
+        run: gh pr merge --auto --merge "$PR_URL"
+
+  refresh-stale-dependabot-prs:
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Refresh open Dependabot PRs after master moves
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          set -euo pipefail
+          mapfile -t prs < <(gh pr list --repo "${{ github.repository }}" --state open --author app/dependabot --json number --jq '.[].number')
+          for pr in "${prs[@]}"; do
+            echo "Updating Dependabot PR #${pr}"
+            gh pr update-branch "$pr" --repo "${{ github.repository }}" || true
+            gh pr merge --auto --merge "$pr" --repo "${{ github.repository }}" || true
+          done

jeles-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,88 @@
+name: Release
+
+# Publishes to PyPI when a version tag is pushed (e.g. `git tag v0.1.0 && git push --tags`).
+#
+# The version is NOT stored in pyproject.toml — hatch-vcs derives it from the
+# tag (see [tool.hatch.version]). The tag is therefore the only place a release
+# number is decided, which is what makes the assertion below meaningful rather
+# than circular: it re-derives from the built artifact and compares.
+#
+# Uses PyPI Trusted Publishing (OIDC) — no API token is stored in the repo,
+# matching willow-mcp. One-time setup before the first release:
+#   1. On PyPI: add a *pending publisher* for project `jeles`, this repo,
+#      workflow `release.yml`, environment `pypi`. (Pending, because the project
+#      does not exist on PyPI until the first upload.)
+#   2. Create a GitHub environment named `pypi` (Settings -> Environments).
+# Until that is configured, this workflow is inert — nothing publishes without a tag.
+#
+# NOTE: `jeles` has never been published, so the FIRST tag pushed sets the first
+# released version, and PyPI never allows a version to be reused. Choose it
+# deliberately.
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          # hatch-vcs derives the version from the git tag, so the tags must be
+          # present. The default shallow checkout fetches none of them.
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+
+      - name: Assert the tag matches the built version
+        # kartikeya shipped a v0.0.8 tag whose build produced 0.0.7, and the only
+        # thing that caught it was PyPI refusing the duplicate upload. Fail here
+        # instead, where the error says what is actually wrong.
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          built="$(ls dist/*.tar.gz | sed -E 's|.*/jeles-(.+)\.tar\.gz|\1|')"
+          echo "tag=${tag}  built=${built}"
+          if [ "$tag" != "$built" ]; then
+            echo "::error::tag v${tag} builds version ${built} — refusing to publish"
+            exit 1
+          fi
+
+      - name: Check metadata
+        run: |
+          python -m pip install --upgrade twine
+          twine check dist/*
+
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # required for Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          skip-existing: true

jeles-0.1.0/.github/workflows/tests.yml

@@ -0,0 +1,107 @@
+name: Tests
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+  schedule:
+    # Daily drift catcher, off the :00/:30 peak-load minutes — fleet pattern.
+    - cron: "7 6 * * *"
+  workflow_dispatch: {}
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+
+      - name: Install lint tools
+        run: pip install ruff==0.15.0 bandit
+
+      - name: Ruff (enforced)
+        run: ruff check jeles tests
+
+      - name: Bandit (enforced — tree is clean, keep it that way)
+        run: bandit -r jeles -ll -q
+
+  test-matrix:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    strategy:
+      fail-fast: false
+      matrix:
+        # Floor and current for requires-python >= 3.10.
+        python-version: ["3.10", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          # hatch-vcs derives the version from git; the default shallow checkout
+          # carries no tags and the derived version would be wrong.
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+          cache-dependency-path: pyproject.toml
+
+      - name: Install package
+        run: pip install -e ".[dev]"
+
+      - name: Run tests
+        run: python -m pytest tests/ -q
+
+  # Base `jeles` must install and pass with NO extras — that is the promise that
+  # lets willow-mcp depend on this package without inheriting a version
+  # constraint. Pinning mcp as a hard dependency once made the two unresolvable
+  # together, and no test noticed. This leg notices.
+  no-extras:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+
+      - name: Install with no extras
+        run: pip install -e . pytest
+
+      - name: Assert the base install is dependency-free
+        run: |
+          python - <<'PY'
+          import importlib.util
+          from importlib.metadata import requires
+
+          declared = [r for r in (requires("jeles") or []) if "extra ==" not in r]
+          assert not declared, f"base jeles declared runtime deps: {declared}"
+
+          assert importlib.util.find_spec("mcp") is None, (
+              "the MCP SDK is installed in the no-extras job, so this leg is not "
+              "actually testing the dependency-free install shape"
+          )
+          print("base install is dependency-free and the MCP SDK is absent")
+          PY
+
+      - name: Run tests without the MCP SDK
+        run: python -m pytest tests/ -q
+
+  # Aggregate gate: branch protection requires a single check named "test"
+  # across the whole fleet. Green only when lint and every matrix leg are.
+  test:
+    needs: [test-matrix, lint, no-extras]
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "lint, all matrix legs, and the no-extras install are green"

jeles-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+*.db
+*.db-wal
+*.db-shm
+.pytest_cache/
+*.egg-info/
+*.egg
+build/
+dist/
+data/

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

jeles-0.1.0/NOTICE

@@ -0,0 +1,2 @@
+Jeles
+Copyright 2026 Sean Campbell

jeles-0.1.0/PKG-INFO

@@ -0,0 +1,158 @@
+Metadata-Version: 2.4
+Name: jeles
+Version: 0.1.0
+Summary: Jeles' verified-nugget corpus organ: pure SOIL-backed storage/ranking, a standalone MCP server, best-effort fleet gap-forwarding, and the canonical Jeles persona.
+Project-URL: Homepage, https://github.com/rudi193-cmd/Jeles
+Project-URL: Repository, https://github.com/rudi193-cmd/Jeles
+Project-URL: Issues, https://github.com/rudi193-cmd/Jeles/issues
+Author: Sean Campbell
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: citations,corpus,jeles,librarian,mcp,retrieval,verified-answers,willow
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Text Processing :: Indexing
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: mcp<2.0.0,>=1.6.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Provides-Extra: mcp
+Requires-Dist: mcp<2.0.0,>=1.6.0; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# jeles
+
+The **verified-corpus organ**, extracted from the [Ask Jeles](https://github.com/rudi193-cmd) app into its own installable package — plus the canonical **Jeles persona**.
+
+A *nugget* is a human-verified question/answer pair with citations:
+`{question, answer, sources, verified_by, verified_at, tags}`. This package
+is the settled layer of answers that sits *in front of* a host's live
+search — a confident nugget match answers instantly; everything else falls
+through to the host's own search path unchanged. Misses are logged as
+*gaps* ("I don't know yet") so the corpus knows what it's been asked and
+couldn't answer.
+
+## What's in the organ
+
+| Module | Role |
+| --- | --- |
+| `jeles.corpus` | Pure storage + ranked lookup of verified nuggets and gap logging. **Stdlib-only, no MCP, no network at import.** Reuses willow-mcp's SOIL `Store` SQLite schema at `$WILLOW_STORE_ROOT/<collection>/store.db`. |
+| `jeles.corpus_server` | Standalone FastMCP server over the corpus (`python -m jeles.corpus_server`). Mirrors willow-mcp's shape (`app_id` on every tool) **without depending on willow-mcp**. |
+| `jeles.willow_mcp_client` | Best-effort, fire-and-forget forwarding of gaps into willow-mcp's fleet-wide backlog. Never blocks, never raises; 30s retry cooldown so a single failed connect doesn't permanently disable forwarding. |
+| `jeles.load_persona()` | Loads the canonical Jeles persona JSON (this package is its canonical home). |
+
+## Design principles
+
+1. **The corpus sits in front of live search, it doesn't replace it.** A confident nugget match answers instantly — no search, no LLM call.
+2. **`corpus.py` stays pure.** Storage and ranking have no MCP, no network, no side effects beyond SQLite. Everything MCP-shaped wraps it; it never depends on anything MCP-shaped itself. This is what keeps its tests fast and network-free.
+3. **The corpus is its own standalone MCP server, on purpose.** `corpus_server.py` is a small FastMCP server any stdio client can run directly, mirroring willow-mcp's shape without depending on it.
+4. **Two kinds of "ask," two gap-logging rules.** `search_nuggets()` (passive/background) checks the corpus but never logs a gap on a miss. `ask_corpus()` (deliberate) treats a miss — or a match below `MIN_ASK_SCORE` — as a real gap worth tracking, and logs it.
+5. **Local is the source of truth; the fleet backlog is additive.** `corpus.log_gap()` (synchronous, local SQLite) always runs first and makes the host fully functional offline. `willow_mcp_client.forward_gap()` is a *best-effort* copy into willow-mcp's shared backlog.
+
+## Install
+
+**Base `jeles` has zero runtime dependencies.** The corpus, the persona, and the
+reactions are stdlib-only, so a host can depend on this package without
+inheriting a single version constraint from it. Only the standalone MCP server
+needs the SDK, and it lives behind an extra.
+
+```bash
+pip install jeles           # corpus + persona + reactions. No dependencies.
+pip install "jeles[mcp]"    # adds the MCP SDK, for the standalone server
+pip install -e ".[dev]"     # editable, with pytest and the SDK
+```
+
+Or as a host dependency, straight from git:
+
+```
+jeles @ git+https://github.com/rudi193-cmd/Jeles@main
+```
+
+> **`jeles[mcp]` is pinned to MCP SDK 1.x.** `mcp.server.fastmcp` was removed in
+> SDK 2.0 and `corpus_server.py` has not been ported to
+> `mcp.server.mcpserver.MCPServer` yet, so the extra cannot currently be
+> installed alongside willow-mcp (which requires `mcp>=2`). Base `jeles` can be —
+> that is the whole point of it being dependency-free.
+
+### Versioning
+
+The version comes from the git tag (`hatch-vcs`), not from a literal in
+`pyproject.toml`, and `jeles.__version__` reads it back out of installed package
+metadata. There is exactly one place a release number is decided, so a tag
+cannot disagree with the artifact it builds.
+
+## Usage
+
+### As a library
+
+```python
+from jeles import corpus
+
+corpus.put_nugget(
+    question="What is the primary color in Grove?",
+    answer="The primary color in Grove is #ffffff (white).",
+    sources=["safe-library/themes/grove.json"],
+    verified_by="designer",
+    tags=["color", "grove", "primary"],
+)
+
+hit = corpus.ask_corpus("What is the primary color in Grove?")
+# -> {"found": True, "exact": True, "nugget": {...}, "candidates": [...]}
+
+miss = corpus.ask_corpus("What is the accent color in Tokyo Night?")
+# -> {"found": False, ...}   and the question is logged as a gap
+```
+
+### As a standalone MCP server
+
+```bash
+python -m jeles.corpus_server      # stdio; or use the `jeles-corpus-mcp` console script
+```
+
+Tools: `corpus_ask`, `corpus_search`, `corpus_get`, `corpus_list`, `corpus_put`, `corpus_gaps` — each takes an `app_id` for naming-convention parity with willow-mcp.
+
+### The persona
+
+```python
+import jeles
+persona = jeles.load_persona()   # dict; canonical Jeles persona
+```
+
+## Configuration
+
+| Env var | Default | Effect |
+| --- | --- | --- |
+| `WILLOW_STORE_ROOT` | `~/.willow/store` | Root under which `<collection>/store.db` lives. |
+| `JELES_CORPUS_COLLECTION` | `ask_jeles_corpus` | Nugget collection name (back-compat with Ask Jeles). |
+| `JELES_CORPUS_GAPS_COLLECTION` | `ask_jeles_corpus_gaps` | Local gap-log collection name. |
+| `JELES_CORPUS_APP_ID` | `ask-jeles` | `app_id` used when forwarding gaps to willow-mcp. |
+| `JELES_CORPUS_TOPIC` | `ask-jeles-corpus` | Backlog topic gaps are forwarded under. |
+| `WILLOW_MCP_CMD` | — | Explicit command to launch willow-mcp (else `willow-mcp` on PATH, else `python -m willow_mcp`). |
+| `ASK_JELES_USE_WILLOW_MCP` | `1` | Set to `0`/`false`/`no` to disable fleet gap-forwarding entirely. |
+
+The Ask Jeles-flavored defaults are preserved so an existing store and its
+already-forwarded fleet backlog keep resolving after the extraction.
+
+## Tests
+
+```bash
+pytest -q
+```
+
+`corpus.py`'s tests are fast and network-free by construction; the
+willow-mcp client tests never spin up a real subprocess. An import-purity
+test asserts that importing `jeles.corpus` loads no MCP or network modules.
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE).