ememdev 1.0.0__tar.gz → 1.2.0__tar.gz

{ememdev-1.0.0 → ememdev-1.2.0}/.gitignore

@@ -29,23 +29,25 @@ tls/
 # These patterns prevent the scaffolding from sneaking back in at root.
 # sdks/emem-ts/ has its own legitimate package.json / tsconfig.json /
 # src/ — those are NOT matched here because patterns are anchored to /.
+#
+# Anchoring only holds for git. hatchling re-anchors a root-anchored
+# pattern to whatever directory it is building, so `/src/` here also hit
+# `sdks/emem-py/src` and `sdks/emem-langmem/src`, and both wheels built
+# clean with zero modules in them. ememdev 1.0.0 shipped to PyPI that
+# way: metadata only, `import emem` raised ModuleNotFoundError. Keep
+# root-anchored patterns off any directory name an SDK also uses.
 node_modules/
 dist/
 dist-server/
 .parcel-cache/
 /index.html
-/package.json
 /package-lock.json
 /vite.config.ts
-/tsconfig.json
 /tsconfig.server.json
-/src/
 /server/
 /tests/*.test.ts
 
 # Artifacts (screenshots, generated images) — keep folder, ignore contents
-artifacts/*
-!artifacts/.gitkeep
 
 # Python ad-hoc tools
 __pycache__/
@@ -84,3 +86,6 @@ docs/book/
 
 # 3d-worlds exporter output (samples live under examples/3d-worlds/scenes/)
 examples/3d-worlds/out/
+
+# Agent scratch notes belong in .well-known/agent-notes/, never the repo root.
+/AGENT_*.md

ememdev-1.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 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 Support. 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 support.
+
+   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 2026 Vortx (https://vortx.ai)
+
+   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.

{ememdev-1.0.0 → ememdev-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ememdev
-Version: 1.0.0
+Version: 1.2.0
 Summary: Python client for emem.dev, the agent-native Earth memory protocol
 Project-URL: Homepage, https://emem.dev
 Project-URL: Repository, https://github.com/Vortx-AI/emem
@@ -8,6 +8,7 @@ Project-URL: Documentation, https://emem.dev/agents.md
 Project-URL: Issues, https://github.com/Vortx-AI/emem/issues
 Author-email: Vortx AI Private Limited <avijeet@vortx.ai>
 License: Apache-2.0
+License-File: LICENSE
 Keywords: content-addressed,earth-observation,ed25519,geospatial,mcp,satellite
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
@@ -22,6 +23,9 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Scientific/Engineering :: GIS
 Requires-Python: >=3.9
 Requires-Dist: httpx<1.0,>=0.27
+Provides-Extra: signing
+Requires-Dist: blake3>=0.3; extra == 'signing'
+Requires-Dist: cryptography>=41; extra == 'signing'
 Description-Content-Type: text/markdown
 
 # ememdev: Python client for emem.dev
@@ -29,10 +33,11 @@ Description-Content-Type: text/markdown
 <!-- mcp-name: io.github.Vortx-AI/emem -->
 
 Thin, typed Python client for the [emem.dev](https://emem.dev) Earth memory
-protocol. Wraps the public REST surface (97 documented paths, 94 under
-`/v1/*`) in a single `Client` class that returns parsed JSON verbatim. Every
-ed25519-signed receipt and content-addressed CID is preserved for
-citation and offline verification.
+protocol. Wraps the public REST surface in a single `Client` class that
+returns parsed JSON verbatim. Every ed25519-signed receipt and
+content-addressed CID is preserved for citation and offline verification.
+The current surface is whatever [`/openapi.json`](https://emem.dev/openapi.json)
+lists; this README does not restate a count that would go stale.
 
 ## Install
 
@@ -40,21 +45,27 @@ citation and offline verification.
 pip install ememdev
 ```
 
-The distribution is named `ememdev`; the import package is `emem` (so
-`pip install ememdev`, then `from emem import Client`). To work from a
-checkout instead:
+The distribution and the import package are both named `ememdev` (so
+`pip install ememdev`, then `from ememdev import Client`); the shorter name
+`emem` on PyPI belongs to an unrelated project. To work from a checkout
+instead:
 
 ```bash
 pip install -e sdks/emem-py
 ```
 
 Requires Python 3.9+. The only runtime dependency is
-[`httpx`](https://www.python-httpx.org/).
+[`httpx`](https://www.python-httpx.org/). To sign memory writes (below),
+add the `signing` extra, which pulls `blake3` and `cryptography`:
+
+```bash
+pip install "ememdev[signing]"
+```
 
 ## Quick start
 
 ```python
-from emem import Client
+from ememdev import Client
 
 with Client() as em:
     cell = em.locate("Mount Fuji")["cell64"]
@@ -66,7 +77,7 @@ with Client() as em:
 
 ```python
 import asyncio
-from emem import AsyncClient
+from ememdev import AsyncClient
 
 async def main() -> None:
     async with AsyncClient() as em:
@@ -91,6 +102,50 @@ Geocoder + read primitives, physics solvers, boring lat/lng shortcuts, and
 introspection — see the inline docstring on `emem.client` for the full
 endpoint → method mapping.
 
+## Writing a signed note
+
+Reads are anonymous. Writes into the agent memory namespace are gated by an
+ed25519 `attester` block, and that signature is the one thing the MCP client
+cannot produce for you. `ememdev[signing]` produces it, from a persistent
+identity, so leaving a signed note is one command rather than a hand-rolled
+crypto script.
+
+The identity is resolved once and reused every session, because the key is
+what owns your namespace at `/memories/by_attester/<pubkey8>/...`. Resolution
+order: `EMEM_AGENT_KEY` (a 64-char hex seed or a key-file path), then
+`~/.emem/agent_ed25519.pem` (override the directory with `EMEM_HOME`), minted
+`0600` on first use if absent.
+
+From the command line, for an agent that already speaks to emem over MCP:
+
+```bash
+ememdev whoami          # your pubkey and namespace_root
+
+# emit just the attester block, sign nothing else (no network):
+ememdev sign  --verb create --path /memories/by_attester/<you>/note.md --stdin < note.md
+
+# or sign a create and POST it to /mcp in one step:
+ememdev write --path /memories/by_attester/<you>/note.md --body-file note.md
+```
+
+Or in Python:
+
+```python
+from ememdev import load_or_create_signer
+
+signer = load_or_create_signer()             # persistent identity
+path = f"{signer.namespace_root}/note.md"
+body = b"a durable, signed, citeable note"
+attester = signer.attester_block("create", path, body)
+# POST {path, file_text, kind, attester} to /mcp memory_create.
+```
+
+`str_replace` and `insert` sign the whole file *after* the edit, and `rename`
+binds both ends of the move (`signer.rename_attester_block(old, new)`); see the
+`ememdev.signing` docstring for the per-verb body rule. A write into another
+key's namespace is refused with a 403, and `sign`/`write` refuse it locally
+first.
+
 ## Receipts
 
 Every non-introspection response carries a `receipt` block with:

ememdev-1.2.0/README.md

@@ -0,0 +1,135 @@
+# ememdev: Python client for emem.dev
+
+<!-- mcp-name: io.github.Vortx-AI/emem -->
+
+Thin, typed Python client for the [emem.dev](https://emem.dev) Earth memory
+protocol. Wraps the public REST surface in a single `Client` class that
+returns parsed JSON verbatim. Every ed25519-signed receipt and
+content-addressed CID is preserved for citation and offline verification.
+The current surface is whatever [`/openapi.json`](https://emem.dev/openapi.json)
+lists; this README does not restate a count that would go stale.
+
+## Install
+
+```bash
+pip install ememdev
+```
+
+The distribution and the import package are both named `ememdev` (so
+`pip install ememdev`, then `from ememdev import Client`); the shorter name
+`emem` on PyPI belongs to an unrelated project. To work from a checkout
+instead:
+
+```bash
+pip install -e sdks/emem-py
+```
+
+Requires Python 3.9+. The only runtime dependency is
+[`httpx`](https://www.python-httpx.org/). To sign memory writes (below),
+add the `signing` extra, which pulls `blake3` and `cryptography`:
+
+```bash
+pip install "ememdev[signing]"
+```
+
+## Quick start
+
+```python
+from ememdev import Client
+
+with Client() as em:
+    cell = em.locate("Mount Fuji")["cell64"]
+    facts = em.recall(cell, bands=["copdem30m.elevation_mean"])
+    print(facts["facts"][0]["value"])
+```
+
+## Async
+
+```python
+import asyncio
+from ememdev import AsyncClient
+
+async def main() -> None:
+    async with AsyncClient() as em:
+        out = await em.ask("How tall is Mount Everest?")
+        print(out["answer"])
+
+asyncio.run(main())
+```
+
+## Configuration
+
+| Env var               | Default              | Effect                                      |
+|-----------------------|----------------------|---------------------------------------------|
+| `EMEM_BASE_URL`       | `https://emem.dev`   | Responder root; point at a self-hosted node |
+| `EMEM_TIMEOUT_SECS`   | `180`                | HTTP timeout (matches gateway timeout)      |
+
+You can also pass `base_url=` and `timeout=` directly to the constructor.
+
+## Surface coverage
+
+Geocoder + read primitives, physics solvers, boring lat/lng shortcuts, and
+introspection — see the inline docstring on `emem.client` for the full
+endpoint → method mapping.
+
+## Writing a signed note
+
+Reads are anonymous. Writes into the agent memory namespace are gated by an
+ed25519 `attester` block, and that signature is the one thing the MCP client
+cannot produce for you. `ememdev[signing]` produces it, from a persistent
+identity, so leaving a signed note is one command rather than a hand-rolled
+crypto script.
+
+The identity is resolved once and reused every session, because the key is
+what owns your namespace at `/memories/by_attester/<pubkey8>/...`. Resolution
+order: `EMEM_AGENT_KEY` (a 64-char hex seed or a key-file path), then
+`~/.emem/agent_ed25519.pem` (override the directory with `EMEM_HOME`), minted
+`0600` on first use if absent.
+
+From the command line, for an agent that already speaks to emem over MCP:
+
+```bash
+ememdev whoami          # your pubkey and namespace_root
+
+# emit just the attester block, sign nothing else (no network):
+ememdev sign  --verb create --path /memories/by_attester/<you>/note.md --stdin < note.md
+
+# or sign a create and POST it to /mcp in one step:
+ememdev write --path /memories/by_attester/<you>/note.md --body-file note.md
+```
+
+Or in Python:
+
+```python
+from ememdev import load_or_create_signer
+
+signer = load_or_create_signer()             # persistent identity
+path = f"{signer.namespace_root}/note.md"
+body = b"a durable, signed, citeable note"
+attester = signer.attester_block("create", path, body)
+# POST {path, file_text, kind, attester} to /mcp memory_create.
+```
+
+`str_replace` and `insert` sign the whole file *after* the edit, and `rename`
+binds both ends of the move (`signer.rename_attester_block(old, new)`); see the
+`ememdev.signing` docstring for the per-verb body rule. A write into another
+key's namespace is refused with a 403, and `sign`/`write` refuse it locally
+first.
+
+## Receipts
+
+Every non-introspection response carries a `receipt` block with:
+
+- `responder_pubkey` (ed25519 base32-nopad-lowercase)
+- `signature_b32` (ed25519 over the canonical CBOR preimage)
+- `merkle_root` (BLAKE3 over the fact CIDs)
+- `fact_cids[]` (the BLAKE3 CIDs of every fact returned)
+
+To cite an answer: quote `receipt.fact_cids[0]` and the responder pubkey.
+The signature can be verified offline against the public key at
+`https://emem.dev/.well-known/emem.json`; no callback to the responder is
+required.
+
+## License
+
+Apache-2.0. Same as the upstream protocol.

{ememdev-1.0.0 → ememdev-1.2.0}/pyproject.toml

@@ -4,7 +4,12 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ememdev"
-version = "1.0.0"
+# 1.1.0 adds the offline signing surface (ememdev.signing / ememdev.identity)
+# and the `ememdev` CLI, so an agent can produce a memory-write attester block
+# without a framework. 1.0.1 first superseded the empty 1.0.0 on PyPI (it
+# shipped dist-info and no modules, so `import emem` raised ModuleNotFoundError;
+# PyPI versions are immutable, so the only fix was to supersede it).
+version = "1.2.0"
 description = "Python client for emem.dev, the agent-native Earth memory protocol"
 readme = "README.md"
 requires-python = ">=3.9"
@@ -37,6 +42,18 @@ dependencies = [
     "httpx>=0.27,<1.0",
 ]
 
+# The base client is httpx-only. Signing memory writes needs ed25519 + blake3,
+# which are only pulled when you ask for them. `ememdev.signing` and the
+# `ememdev` CLI's sign/write commands raise a clear install hint without this.
+[project.optional-dependencies]
+signing = [
+    "blake3>=0.3",
+    "cryptography>=41",
+]
+
+[project.scripts]
+ememdev = "ememdev.__main__:main"
+
 [project.urls]
 Homepage = "https://emem.dev"
 Repository = "https://github.com/Vortx-AI/emem"
@@ -44,7 +61,7 @@ Documentation = "https://emem.dev/agents.md"
 Issues = "https://github.com/Vortx-AI/emem/issues"
 
 [tool.hatch.build.targets.wheel]
-packages = ["src/emem"]
+packages = ["src/ememdev"]
 
 [tool.hatch.build.targets.sdist]
-include = ["src/emem", "README.md", "LICENSE"]
+include = ["src/ememdev", "README.md", "LICENSE"]

ememdev-1.2.0/src/ememdev/__init__.py

@@ -0,0 +1,71 @@
+"""ememdev: Python client for the emem.dev Earth memory protocol.
+
+The distribution and the module are both named ``ememdev``, on purpose:
+the shorter name ``emem`` on PyPI belongs to an unrelated project by
+another company, and a module named ``emem`` would collide with it on
+disk if both were installed.
+
+This package wraps the REST surface of the hosted instance at
+https://emem.dev in a thin, typed client. Every call returns the raw JSON
+the server emitted; nothing is reshaped, so the ed25519-signed receipts
+and content-addressed CIDs are preserved verbatim for citation and
+offline verification.
+
+The responder enumerates its own surface: GET /openapi.json lists every
+documented path and POST /mcp `tools/list` every MCP tool. Those are the
+counts to quote, since a number written down here goes stale the next
+time a route lands.
+
+Quick start:
+
+    from ememdev import Client
+
+    em = Client()  # defaults to https://emem.dev
+    cell = em.locate("Mount Fuji")["cell64"]
+    facts = em.recall(cell, bands=["copdem30m.elevation_mean"])
+    print(facts["facts"][0]["value"])
+"""
+
+from importlib.metadata import PackageNotFoundError, version as _pkg_version
+
+from .client import AsyncClient, Client, EmemError, EmemHTTPError
+
+__all__ = [
+    "AsyncClient",
+    "Client",
+    "EmemError",
+    "EmemHTTPError",
+    # Signing surface, resolved lazily below so `import ememdev` needs no
+    # crypto. Available with the `signing` extra: pip install ememdev[signing].
+    "EmemSigner",
+    "load_signer",
+    "load_or_create_signer",
+]
+
+# Keep the base import dependency-light: the client is httpx-only, and the
+# signer pulls blake3 + cryptography. Resolve the signing names on first
+# access (PEP 562) so `from ememdev import EmemSigner` works when the extra
+# is installed and gives a clear install hint when it is not.
+_SIGNING_EXPORTS = {
+    "EmemSigner": ("ememdev.signing", "EmemSigner"),
+    "load_signer": ("ememdev.identity", "load_signer"),
+    "load_or_create_signer": ("ememdev.identity", "load_or_create_signer"),
+}
+
+
+def __getattr__(name: str):
+    target = _SIGNING_EXPORTS.get(name)
+    if target is None:
+        raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
+    import importlib
+
+    module, attr = target
+    return getattr(importlib.import_module(module), attr)
+
+# Single source of truth: the installed distribution's version, which comes
+# from pyproject.toml. Keeps __version__ and the client User-Agent from
+# drifting out of sync with what actually ships to PyPI.
+try:
+    __version__ = _pkg_version("ememdev")
+except PackageNotFoundError:  # running from a source checkout, not installed
+    __version__ = "0+unknown"