next-wiki-hermes-memory 0.1.0__tar.gz

next_wiki_hermes_memory-0.1.0/PKG-INFO

@@ -0,0 +1,117 @@
+Metadata-Version: 2.4
+Name: next-wiki-hermes-memory
+Version: 0.1.0
+Summary: Hermes MemoryProvider backed by next-wiki's scoped memory API
+Author: next-wiki contributors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/hugogu/next-wiki
+Project-URL: Documentation, https://github.com/hugogu/next-wiki/blob/main/docs/hermes-memory-provider.md
+Project-URL: Repository, https://github.com/hugogu/next-wiki
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+
+# next-wiki Hermes Memory Provider
+
+Use a [next-wiki](https://github.com/hugogu/next-wiki) instance as the durable,
+inspectable memory destination for one configured agent identity. Hermes is the
+first client integration. Records are stored as immutable, append-only Raw
+entries with published revisions. Each memory-provider API key is bound
+server-side to one memory destination and identity, so a client cannot select
+another profile's namespace through a tool argument or URL.
+
+## Install and activate
+
+1. Enable **LLM Wiki** writing mode so the shared Raw space is available. Then
+   open **User Center → API Keys** and select **Memory provider**. Set the
+   non-secret **Agent identity** (normally `hermes`). The preset grants only `memory.read`, `memory.write`, and
+   `memory.delete`; it does not grant generic page access. Copy the secret once.
+2. Install the provider:
+
+   ```bash
+   python -m pip install next-wiki-hermes-memory
+   hermes memory setup
+   hermes memory status
+   ```
+
+3. Select `next-wiki` in the Hermes picker. Enter the versioned API base URL
+   (for example `https://wiki.example.com/api/v1`) and enter the key only at
+   Hermes's secret prompt. Hermes exposes it as `NEXT_WIKI_MEMORY_API_KEY`.
+
+The primary distribution path is the Python entry point
+`hermes_agent.memory_providers`. For development only, a package can be placed
+under `$HERMES_HOME/plugins/next-wiki` or `./.hermes/plugins/next-wiki` (the
+latter needs `HERMES_ENABLE_PROJECT_PLUGINS=1`). Do not install two providers
+with the `next-wiki` slug: Hermes uses discovery precedence and reports the
+first matching provider.
+
+## Safe configuration and checks
+
+The provider writes only non-secret settings (including `agent_identity`) to
+`$HERMES_HOME/next-wiki-memory.json`; the secret belongs in Hermes's profile
+secret store. It never accepts a key as a command-line argument.
+
+```bash
+# Preview a local configuration without writing it or contacting the Wiki.
+next-wiki-hermes-memory init --wiki-url https://wiki.example.com/api/v1 --dry-run
+
+# Active-provider commands, after selecting next-wiki in Hermes.
+hermes next-wiki status  # local only; never prints the key
+hermes next-wiki check   # validates TLS, authentication, binding, and scopes
+```
+
+`status` is intentionally offline. `check` returns repair guidance for invalid
+or revoked keys, insufficient scopes, redirects, timeouts, an unavailable
+route, and incompatible versions without echoing response bodies or secrets.
+
+| Deployment | API URL example |
+| --- | --- |
+| Local Hermes + local Wiki | `http://127.0.0.1:3000/api/v1` |
+| Remote / reverse-proxied Wiki | `https://wiki.example.com/api/v1` |
+| Hermes in another container | the Wiki's reachable container/DNS address, normally HTTPS behind the proxy |
+
+Remote URLs must use HTTPS. A loopback URL is valid only when Hermes runs in
+the same network namespace as the Wiki; Docker containers generally cannot use
+the host's `127.0.0.1`.
+
+## Memory behavior and privacy
+
+Hermes receives three namespaced tools:
+
+- `next_wiki_memory_search(query, limit)` recalls only the key's destination;
+- `next_wiki_memory_save(content, title?, tags?)` writes an immutable Raw
+  memory record; and
+- `next_wiki_memory_forget(memory_id, reason?)` hides a record from future
+  recall in that same destination. The original Raw entry is never changed.
+
+Recall results contain a canonical Wiki revision citation. Automatic turn
+capture is disabled by default. If it is enabled, the provider preserves only
+user and assistant text, excludes tool calls/results and system content, and
+does not capture delegated/non-primary agent contexts.
+
+Strict pre-compression checkpoints are opt-in and require a Hermes runtime that
+supports checkpoint API v2. When enabled, compression must not treat a
+checkpoint as successful until the queued capture reports `durable`; a failed
+or timed-out capture fails closed. Keep strict mode off on older Hermes
+versions, and verify it after every Hermes upgrade.
+
+## Rotation, recovery, and backups
+
+Create a new dedicated key, re-run setup, confirm `hermes next-wiki check`,
+then revoke the old key in **User Center → API Keys**. Revocation stops future
+access immediately. Forget changes only the Hermes record's recall state, so
+the immutable Raw entry retains its original content and revisions for
+administrators according to the Wiki's Raw-space retention policy.
+
+Back up the Wiki database and content store with the normal deployment backup
+procedure; memory pages and their revision citations are included. For full
+server and reverse-proxy guidance, see
+[the deployment guide](../../docs/hermes-memory-provider.md).

next_wiki_hermes_memory-0.1.0/README.md

@@ -0,0 +1,96 @@
+# next-wiki Hermes Memory Provider
+
+Use a [next-wiki](https://github.com/hugogu/next-wiki) instance as the durable,
+inspectable memory destination for one configured agent identity. Hermes is the
+first client integration. Records are stored as immutable, append-only Raw
+entries with published revisions. Each memory-provider API key is bound
+server-side to one memory destination and identity, so a client cannot select
+another profile's namespace through a tool argument or URL.
+
+## Install and activate
+
+1. Enable **LLM Wiki** writing mode so the shared Raw space is available. Then
+   open **User Center → API Keys** and select **Memory provider**. Set the
+   non-secret **Agent identity** (normally `hermes`). The preset grants only `memory.read`, `memory.write`, and
+   `memory.delete`; it does not grant generic page access. Copy the secret once.
+2. Install the provider:
+
+   ```bash
+   python -m pip install next-wiki-hermes-memory
+   hermes memory setup
+   hermes memory status
+   ```
+
+3. Select `next-wiki` in the Hermes picker. Enter the versioned API base URL
+   (for example `https://wiki.example.com/api/v1`) and enter the key only at
+   Hermes's secret prompt. Hermes exposes it as `NEXT_WIKI_MEMORY_API_KEY`.
+
+The primary distribution path is the Python entry point
+`hermes_agent.memory_providers`. For development only, a package can be placed
+under `$HERMES_HOME/plugins/next-wiki` or `./.hermes/plugins/next-wiki` (the
+latter needs `HERMES_ENABLE_PROJECT_PLUGINS=1`). Do not install two providers
+with the `next-wiki` slug: Hermes uses discovery precedence and reports the
+first matching provider.
+
+## Safe configuration and checks
+
+The provider writes only non-secret settings (including `agent_identity`) to
+`$HERMES_HOME/next-wiki-memory.json`; the secret belongs in Hermes's profile
+secret store. It never accepts a key as a command-line argument.
+
+```bash
+# Preview a local configuration without writing it or contacting the Wiki.
+next-wiki-hermes-memory init --wiki-url https://wiki.example.com/api/v1 --dry-run
+
+# Active-provider commands, after selecting next-wiki in Hermes.
+hermes next-wiki status  # local only; never prints the key
+hermes next-wiki check   # validates TLS, authentication, binding, and scopes
+```
+
+`status` is intentionally offline. `check` returns repair guidance for invalid
+or revoked keys, insufficient scopes, redirects, timeouts, an unavailable
+route, and incompatible versions without echoing response bodies or secrets.
+
+| Deployment | API URL example |
+| --- | --- |
+| Local Hermes + local Wiki | `http://127.0.0.1:3000/api/v1` |
+| Remote / reverse-proxied Wiki | `https://wiki.example.com/api/v1` |
+| Hermes in another container | the Wiki's reachable container/DNS address, normally HTTPS behind the proxy |
+
+Remote URLs must use HTTPS. A loopback URL is valid only when Hermes runs in
+the same network namespace as the Wiki; Docker containers generally cannot use
+the host's `127.0.0.1`.
+
+## Memory behavior and privacy
+
+Hermes receives three namespaced tools:
+
+- `next_wiki_memory_search(query, limit)` recalls only the key's destination;
+- `next_wiki_memory_save(content, title?, tags?)` writes an immutable Raw
+  memory record; and
+- `next_wiki_memory_forget(memory_id, reason?)` hides a record from future
+  recall in that same destination. The original Raw entry is never changed.
+
+Recall results contain a canonical Wiki revision citation. Automatic turn
+capture is disabled by default. If it is enabled, the provider preserves only
+user and assistant text, excludes tool calls/results and system content, and
+does not capture delegated/non-primary agent contexts.
+
+Strict pre-compression checkpoints are opt-in and require a Hermes runtime that
+supports checkpoint API v2. When enabled, compression must not treat a
+checkpoint as successful until the queued capture reports `durable`; a failed
+or timed-out capture fails closed. Keep strict mode off on older Hermes
+versions, and verify it after every Hermes upgrade.
+
+## Rotation, recovery, and backups
+
+Create a new dedicated key, re-run setup, confirm `hermes next-wiki check`,
+then revoke the old key in **User Center → API Keys**. Revocation stops future
+access immediately. Forget changes only the Hermes record's recall state, so
+the immutable Raw entry retains its original content and revisions for
+administrators according to the Wiki's Raw-space retention policy.
+
+Back up the Wiki database and content store with the normal deployment backup
+procedure; memory pages and their revision citations are included. For full
+server and reverse-proxy guidance, see
+[the deployment guide](../../docs/hermes-memory-provider.md).

next_wiki_hermes_memory-0.1.0/pyproject.toml

@@ -0,0 +1,45 @@
+[build-system]
+requires = ["setuptools>=69"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "next-wiki-hermes-memory"
+version = "0.1.0"
+description = "Hermes MemoryProvider backed by next-wiki's scoped memory API"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+authors = [{ name = "next-wiki contributors" }]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+]
+
+[project.urls]
+Homepage = "https://github.com/hugogu/next-wiki"
+Documentation = "https://github.com/hugogu/next-wiki/blob/main/docs/hermes-memory-provider.md"
+Repository = "https://github.com/hugogu/next-wiki"
+
+[project.scripts]
+next-wiki-hermes-memory = "next_wiki_memory.cli:main"
+
+[project.optional-dependencies]
+dev = ["build>=1.2", "pytest>=8"]
+
+[project.entry-points."hermes_agent.memory_providers"]
+next-wiki = "next_wiki_memory:register"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"
+
+[tool.setuptools]
+package-dir = { "" = "src" }
+include-package-data = true
+
+[tool.setuptools.packages.find]
+where = ["src"]

next_wiki_hermes_memory-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/PKG-INFO

@@ -0,0 +1,117 @@
+Metadata-Version: 2.4
+Name: next-wiki-hermes-memory
+Version: 0.1.0
+Summary: Hermes MemoryProvider backed by next-wiki's scoped memory API
+Author: next-wiki contributors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/hugogu/next-wiki
+Project-URL: Documentation, https://github.com/hugogu/next-wiki/blob/main/docs/hermes-memory-provider.md
+Project-URL: Repository, https://github.com/hugogu/next-wiki
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+
+# next-wiki Hermes Memory Provider
+
+Use a [next-wiki](https://github.com/hugogu/next-wiki) instance as the durable,
+inspectable memory destination for one configured agent identity. Hermes is the
+first client integration. Records are stored as immutable, append-only Raw
+entries with published revisions. Each memory-provider API key is bound
+server-side to one memory destination and identity, so a client cannot select
+another profile's namespace through a tool argument or URL.
+
+## Install and activate
+
+1. Enable **LLM Wiki** writing mode so the shared Raw space is available. Then
+   open **User Center → API Keys** and select **Memory provider**. Set the
+   non-secret **Agent identity** (normally `hermes`). The preset grants only `memory.read`, `memory.write`, and
+   `memory.delete`; it does not grant generic page access. Copy the secret once.
+2. Install the provider:
+
+   ```bash
+   python -m pip install next-wiki-hermes-memory
+   hermes memory setup
+   hermes memory status
+   ```
+
+3. Select `next-wiki` in the Hermes picker. Enter the versioned API base URL
+   (for example `https://wiki.example.com/api/v1`) and enter the key only at
+   Hermes's secret prompt. Hermes exposes it as `NEXT_WIKI_MEMORY_API_KEY`.
+
+The primary distribution path is the Python entry point
+`hermes_agent.memory_providers`. For development only, a package can be placed
+under `$HERMES_HOME/plugins/next-wiki` or `./.hermes/plugins/next-wiki` (the
+latter needs `HERMES_ENABLE_PROJECT_PLUGINS=1`). Do not install two providers
+with the `next-wiki` slug: Hermes uses discovery precedence and reports the
+first matching provider.
+
+## Safe configuration and checks
+
+The provider writes only non-secret settings (including `agent_identity`) to
+`$HERMES_HOME/next-wiki-memory.json`; the secret belongs in Hermes's profile
+secret store. It never accepts a key as a command-line argument.
+
+```bash
+# Preview a local configuration without writing it or contacting the Wiki.
+next-wiki-hermes-memory init --wiki-url https://wiki.example.com/api/v1 --dry-run
+
+# Active-provider commands, after selecting next-wiki in Hermes.
+hermes next-wiki status  # local only; never prints the key
+hermes next-wiki check   # validates TLS, authentication, binding, and scopes
+```
+
+`status` is intentionally offline. `check` returns repair guidance for invalid
+or revoked keys, insufficient scopes, redirects, timeouts, an unavailable
+route, and incompatible versions without echoing response bodies or secrets.
+
+| Deployment | API URL example |
+| --- | --- |
+| Local Hermes + local Wiki | `http://127.0.0.1:3000/api/v1` |
+| Remote / reverse-proxied Wiki | `https://wiki.example.com/api/v1` |
+| Hermes in another container | the Wiki's reachable container/DNS address, normally HTTPS behind the proxy |
+
+Remote URLs must use HTTPS. A loopback URL is valid only when Hermes runs in
+the same network namespace as the Wiki; Docker containers generally cannot use
+the host's `127.0.0.1`.
+
+## Memory behavior and privacy
+
+Hermes receives three namespaced tools:
+
+- `next_wiki_memory_search(query, limit)` recalls only the key's destination;
+- `next_wiki_memory_save(content, title?, tags?)` writes an immutable Raw
+  memory record; and
+- `next_wiki_memory_forget(memory_id, reason?)` hides a record from future
+  recall in that same destination. The original Raw entry is never changed.
+
+Recall results contain a canonical Wiki revision citation. Automatic turn
+capture is disabled by default. If it is enabled, the provider preserves only
+user and assistant text, excludes tool calls/results and system content, and
+does not capture delegated/non-primary agent contexts.
+
+Strict pre-compression checkpoints are opt-in and require a Hermes runtime that
+supports checkpoint API v2. When enabled, compression must not treat a
+checkpoint as successful until the queued capture reports `durable`; a failed
+or timed-out capture fails closed. Keep strict mode off on older Hermes
+versions, and verify it after every Hermes upgrade.
+
+## Rotation, recovery, and backups
+
+Create a new dedicated key, re-run setup, confirm `hermes next-wiki check`,
+then revoke the old key in **User Center → API Keys**. Revocation stops future
+access immediately. Forget changes only the Hermes record's recall state, so
+the immutable Raw entry retains its original content and revisions for
+administrators according to the Wiki's Raw-space retention policy.
+
+Back up the Wiki database and content store with the normal deployment backup
+procedure; memory pages and their revision citations are included. For full
+server and reverse-proxy guidance, see
+[the deployment guide](../../docs/hermes-memory-provider.md).

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/SOURCES.txt

@@ -0,0 +1,24 @@
+README.md
+pyproject.toml
+src/next_wiki_hermes_memory.egg-info/PKG-INFO
+src/next_wiki_hermes_memory.egg-info/SOURCES.txt
+src/next_wiki_hermes_memory.egg-info/dependency_links.txt
+src/next_wiki_hermes_memory.egg-info/entry_points.txt
+src/next_wiki_hermes_memory.egg-info/requires.txt
+src/next_wiki_hermes_memory.egg-info/top_level.txt
+src/next_wiki_memory/__init__.py
+src/next_wiki_memory/api_client.py
+src/next_wiki_memory/cli.py
+src/next_wiki_memory/config.py
+src/next_wiki_memory/config_schema.py
+src/next_wiki_memory/redaction.py
+tests/test_api_client.py
+tests/test_availability.py
+tests/test_capture_lifecycle.py
+tests/test_checkpoints.py
+tests/test_cli.py
+tests/test_config.py
+tests/test_config_schema.py
+tests/test_provider.py
+tests/test_provider_registration.py
+tests/test_tools.py

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/entry_points.txt

@@ -0,0 +1,5 @@
+[console_scripts]
+next-wiki-hermes-memory = next_wiki_memory.cli:main
+
+[hermes_agent.memory_providers]
+next-wiki = next_wiki_memory:register

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/requires.txt

@@ -0,0 +1,4 @@
+
+[dev]
+build>=1.2
+pytest>=8

next_wiki_hermes_memory-0.1.0/src/next_wiki_hermes_memory.egg-info/top_level.txt

@@ -0,0 +1 @@
+next_wiki_memory