hermes-tenuo 0.1.0__tar.gz

hermes_tenuo-0.1.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 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 2026 Tenuo 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.

hermes_tenuo-0.1.0/PKG-INFO

@@ -0,0 +1,367 @@
+Metadata-Version: 2.4
+Name: hermes-tenuo
+Version: 0.1.0
+Summary: Tenuo authorization plugin for Hermes Agent
+Author: Tenuo AI
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/tenuo-ai/hermes-tenuo
+Project-URL: Documentation, https://github.com/tenuo-ai/hermes-tenuo#readme
+Project-URL: Repository, https://github.com/tenuo-ai/hermes-tenuo
+Project-URL: Issues, https://github.com/tenuo-ai/hermes-tenuo/issues
+Keywords: hermes,authorization,agents,security,warrants,tenuo
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+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 :: Security
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: tenuo>=0.3.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-asyncio; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Dynamic: license-file
+
+# hermes-tenuo
+
+[![CI](https://github.com/tenuo-ai/hermes-tenuo/actions/workflows/ci.yml/badge.svg)](https://github.com/tenuo-ai/hermes-tenuo/actions/workflows/ci.yml)
+
+**Give each Hermes agent a signed, expiring permission slip. Nothing outside it runs.**
+
+A [Tenuo](https://github.com/tenuo-ai/tenuo) warrant sits in front of every
+Hermes tool call. Each call is checked at the argument level before the
+handler runs. A `delegate_task` child is a grant from the parent warrant,
+verified as a chain. Gateway users each carry their own warrant. Keys,
+warrants, and decisions stay local.
+
+See it without installing Hermes or talking to a model:
+
+```bash
+pip install "git+https://github.com/tenuo-ai/hermes-tenuo.git"
+hermes-tenuo demo
+```
+
+```text
+Give each Hermes agent a signed, expiring permission slip.
+Nothing outside it runs. No Hermes process, no API key.
+
+== Cron ==
+Nightly job: read /data/reports, write /tmp/nightly, then stop.
+  ALLOW  read_file  path=/data/reports/q3.csv
+  ALLOW  write_file  path=/tmp/nightly/report.md
+  DENY   read_file  path=/etc/passwd
+         Constraint 'path' not satisfied: value does not match constraint
+  DENY   terminal  command=ls
+         Tool 'terminal' is not authorized
+
+== delegate_task ==
+Orchestrator grants web_search to the researcher. The chain is verified.
+  [orchestrator] ALLOW  read_file  path=/data/input.csv
+  [orchestrator] ALLOW  delegate_task  task=research q3  context=web_search only
+  [researcher] ALLOW  web_search  query=AI papers 2026
+  [researcher] DENY   write_file  path=/data/output/x.md
+         Tool 'write_file' is not authorized
+
+== Gateway ==
+Analyst and viewer on the same server, different warrants.
+  [analyst] ALLOW  read_file  path=/data/reports/q1.csv
+  [analyst] DENY   write_file  path=/data/output/x.txt
+         Tool 'write_file' is not authorized
+  [viewer] ALLOW  read_file  path=/data/public/faq.md
+  [viewer] DENY   read_file  path=/data/reports/q1.csv
+         Constraint 'path' not satisfied: value does not match constraint
+```
+
+That `DENY` line is the tool result Hermes gives the model. The handler
+never runs:
+
+```text
+read_file  path=/etc/passwd
+Constraint 'path' not satisfied: value does not match constraint
+```
+
+## Install into Hermes
+
+**1. Install.**
+
+```bash
+# into the venv Hermes uses (pulls in tenuo):
+pip install "git+https://github.com/tenuo-ai/hermes-tenuo.git"
+
+# or as a directory plugin under ~/.hermes/plugins:
+hermes plugins install tenuo-ai/hermes-tenuo
+pip install "tenuo>=0.3.0"   # Hermes does not install plugin dependencies
+```
+
+Requires Hermes Agent 0.20 or newer (tested against upstream, September 2026).
+The pip route installs `tenuo>=0.3.0` for you; the directory route needs the
+extra `pip install` line above.
+
+**2. Mint a warrant.** This generates a key pair and a warrant, and prints
+the exact config block to paste.
+
+```bash
+hermes-tenuo mint --ttl 1h \
+  --allow read_file:path=/data \
+  --allow web_search
+```
+
+```yaml
+# ~/.hermes/config.yaml   (printed by the command above)
+plugins:
+  enabled:
+    - hermes-tenuo
+  entries:
+    hermes-tenuo:
+      warrant: <base64>            # or a path to a .warrant file
+      trusted_root: <base64>       # the public key that signed it
+      signing_key_env: TENUO_SIGNING_KEY
+```
+
+```bash
+export TENUO_SIGNING_KEY=<printed by mint>
+```
+
+**3. Check the wiring, then run Hermes.**
+
+```bash
+hermes-tenuo doctor
+hermes
+```
+
+Ask the agent to read `/etc/passwd`. It gets the same denial as the tool
+result. Load `skill_view("hermes-tenuo:tenuo-scope")` to mint a warrant
+for a cron job, a `delegate_task` child, or a gateway session.
+
+## Scoping arguments
+
+Each `--allow` names a tool and, optionally, constraints on its arguments.
+A tool with no constraints is allowed with any arguments.
+
+| Syntax | Meaning | Example |
+|---|---|---|
+| `tool` | any arguments | `--allow web_search` |
+| `tool:arg=/path` | argument must be that path or under it (traversal-safe) | `--allow read_file:path=/data` |
+| `tool:arg=glob*` | argument must match the glob | `--allow web_search:query=acme*` |
+| `tool:arg=a\|b\|c` | argument must be one of the choices | `--allow git:action=status\|diff\|log` |
+| `tool:arg=value` | argument must match exactly | `--allow write_file:mode=w` |
+| `tool:arg=*` | that argument may be anything | `--allow memory:action=*` |
+| `tool:a=..,b=..` | several constraints on one tool | `--allow write_file:path=/tmp/out,mode=w` |
+
+Any argument the warrant does not name is unconstrained for that tool. The
+`--ttl` flag takes `30m`, `1h`, `7d`, and so on (default `24h`).
+
+For anything the flag syntax cannot express, mint in Python with the full
+constraint set (numeric ranges, case-insensitive paths, and more):
+
+```python
+import base64, os
+from tenuo import SigningKey, Warrant, Subpath, Pattern, Range
+
+control_key = SigningKey.generate()   # keep private; its public key is trusted_root
+agent_key = SigningKey.generate()     # export its secret as TENUO_SIGNING_KEY
+
+warrant = (
+    Warrant.mint_builder()
+    .holder(agent_key.public_key)
+    .capability("read_file", path=Subpath("/data"))
+    .capability("web_search", query=Pattern("acme*"))
+    .capability("scale_cluster", replicas=Range.max_value(10))
+    .ttl(3600)
+    .mint(control_key)
+)
+
+path = os.path.expanduser("~/.hermes/tenuo/warrant")
+os.makedirs(os.path.dirname(path), exist_ok=True)
+with open(path, "w") as f:
+    f.write(base64.b64encode(warrant.to_bytes()).decode())
+```
+
+Point `warrant:` at that file. Set `trusted_root` to the base64 of
+`control_key.public_key.to_bytes()` and `TENUO_SIGNING_KEY` to the base64 of
+`agent_key.secret_key_bytes()`.
+
+## What it unlocks
+
+| Scenario | What you do | What you get |
+|---|---|---|
+| **Cron and scheduled agents** | Mint with `--ttl` matching the job window | The job cannot keep acting after it should be done, even if it is still running |
+| **Subagents via `delegate_task`** | Grant from the parent (`grant_builder`) | The child hop is verified as a chain; a researcher cannot suddenly `write_file` |
+| **Multi-user gateways** | Call `guard.set_session_warrant(session_id, warrant)` when a session starts | Per-user permissions, isolated per session, cleared on session end |
+| **Kanban workers** | Drop `~/.hermes/tenuo/warrants/<task_id>.warrant` | The worker loads its own warrant; a denial auto-blocks the task on the board |
+| **Fleet rollout** | Pin `warrant`, `trusted_root`, `on_denial` in managed scope | Users cannot loosen them from `~/.hermes/config.yaml` |
+
+Runnable versions of the first three live in
+[`examples/`](https://github.com/tenuo-ai/hermes-tenuo/tree/main/examples).
+
+## See what your agent actually calls
+
+Every decision is appended to a local JSONL audit log, on by default at
+`~/.hermes/tenuo/audit.jsonl` (profile-aware under `HERMES_HOME`). No account
+needed.
+
+```bash
+hermes-tenuo audit --last 20          # one line per tool call
+hermes-tenuo audit --denied           # only what the warrant blocked
+hermes-tenuo audit --json | jq ...    # raw records
+```
+
+```text
+2026-09-12 10:00:00  ALLOW  read_file  path=/data/q3.md
+2026-09-12 10:00:01  DENY   terminal  command=ls  — Tool 'terminal' is not authorized
+```
+
+Not sure what to allow yet? Set `on_denial: log`. Every call is still
+checked and recorded, but nothing is blocked. Run the agent, read the denied
+lines, tighten the warrant, then remove the line (the default is `block`).
+
+```yaml
+plugins:
+  entries:
+    hermes-tenuo:
+      warrant: ~/.hermes/tenuo/warrant
+      trusted_root: <base64>
+      on_denial: log
+```
+
+## How it works
+
+| Hermes hook | What hermes-tenuo does there |
+|---|---|
+| `pre_tool_call` | Verifies the tool name and arguments against the session's warrant. On denial, returns `{"action": "block", "message": ...}`; the handler never runs. |
+| `post_tool_call` | Adds timing to the recorded decision and writes the audit record. |
+| `subagent_start` | Hands the `child_warrant` to the new child session. |
+| `on_session_end` | Clears any per-session warrant set with `guard.set_session_warrant()`, so gateway users never share one. |
+
+The decision itself runs in Tenuo's Rust core: signature, expiry, holder
+proof-of-possession, and every argument constraint. The plugin holds only the
+issuer's **public** key. It never sees the key that minted the warrant.
+
+Denials are returned to the model as the tool result, so the agent can
+explain what it was not allowed to do. Raise the `hermes_tenuo` logger level
+to see the same lines as an operator.
+
+## Coverage
+
+On upstream Hermes, enforcement runs at `pre_tool_call`. That covers every
+tool call made through the agent loop, including the tools `run_agent.py`
+handles before the registry (`todo`, `memory`, `session_search`,
+`delegate_task`). It does not cover:
+
+- callers that pass `skip_pre_tool_call_hook=True`;
+- plugins that call `registry.dispatch()` directly;
+- the `execute_code` sandbox's internal tool dispatch.
+
+A registry-level hook that closes all three is proposed upstream in
+[hermes-agent#32719](https://github.com/NousResearch/hermes-agent/pull/32719).
+The plugin detects it at load time and uses it automatically, and
+`hermes-tenuo doctor` reports which path is active.
+
+Neither path inspects what an `execute_code` script does on its own, such as
+`subprocess.run(...)`. Use a container backend (Docker, Modal, Daytona) for
+that threat model.
+
+## CLI
+
+```bash
+hermes-tenuo demo        # local allow/deny transcript (no Hermes process)
+hermes-tenuo mint --allow TOOL[:ARG=VALUE,...] [--allow ...] [--ttl 1h] [--output full|yaml|env]
+hermes-tenuo status      # what the plugin will load from config and env
+hermes-tenuo verify      # decode and check the current warrant
+hermes-tenuo doctor      # end-to-end install check
+hermes-tenuo audit [--last N] [--denied] [--json] [--path FILE]
+```
+
+Run `doctor` from the same venv Hermes uses. It checks plugin discovery,
+config wiring, warrant validity, that the signing key matches the warrant
+holder, and which enforcement path is active. Run it after every install.
+
+## Configuration reference
+
+All keys live under `plugins.entries.hermes-tenuo`. Each has an environment
+variable equivalent.
+
+| Key | Env | Meaning |
+|---|---|---|
+| `warrant` | `TENUO_WARRANT` | Base64 warrant, or a path to a file containing one. Required for enforcement. |
+| `trusted_root` | `TENUO_TRUSTED_ROOT` | Base64 public key of the issuer. Warrants signed by anything else are rejected. |
+| `signing_key_env` | | Name of the env var holding the agent's Ed25519 secret key. Default `TENUO_SIGNING_KEY`. |
+| `child_warrant` | `TENUO_CHILD_WARRANT` | Warrant handed to sessions spawned by `delegate_task`. |
+| `on_denial` | | `block` (default) or `log`. |
+| `audit_log` | `TENUO_AUDIT_LOG` | Path of the JSONL audit log, or `false` to disable. Default `$HERMES_HOME/tenuo/audit.jsonl`. |
+
+Keep secret key material in env vars or a secrets manager, never in
+`config.yaml`.
+
+## Things to know
+
+- **Enabled but unconfigured is a no-op.** Without a `warrant`, the plugin
+  loads, logs a warning, and enforces nothing. `doctor` fails that check.
+- **Multiplexed profiles.** Under `gateway.multiplex_profiles`, `TENUO_*`
+  values are read through Hermes `get_secret`, so put each profile's keys in
+  that profile's `.env`. A secondary profile does not inherit the launch
+  profile's credentials.
+- **Rotate by re-minting.** The control key is not saved by `mint`. To change
+  scope, mint a new warrant and replace the config values; the old warrant
+  stops being accepted when you change `trusted_root`, or when its TTL ends.
+
+## Managed scope (fleet and multi-user)
+
+Hermes overlays a root-owned `/etc/hermes/config.yaml` on every user's
+config. hermes-tenuo reads its keys through the same loader, so an
+administrator can pin the warrant and trust anchor for the whole fleet:
+
+```yaml
+# /etc/hermes/config.yaml  (root-owned)
+plugins:
+  entries:
+    hermes-tenuo:
+      warrant: /etc/hermes/tenuo/fleet.warrant
+      trusted_root: <base64>
+      on_denial: block
+```
+
+Pin `warrant`, `trusted_root`, and `on_denial`. Leave `signing_key_env` to
+the environment. Override the managed directory with `HERMES_MANAGED_DIR` for
+containers or non-standard layouts.
+
+## Connecting a control plane (optional)
+
+Everything above runs from files and environment variables on one machine.
+That is the right shape for one developer and a handful of agents. Once you
+run a fleet of Hermes agents, cron jobs, and gateway users, the hard part
+stops being the check itself and becomes operating the authority around it:
+who may mint production warrants, how keys rotate, how a bad warrant is
+pulled back before its TTL ends, and where you look when something was
+denied at 3 a.m. A Tenuo control plane takes that over.
+
+When `TENUO_CONNECT_TOKEN` is set, the Tenuo SDK inside this plugin connects
+on its own and every allow and deny decision from every Hermes agent streams
+there, with nothing else to configure. On top of that stream the control
+plane gives you:
+
+- **Revocation before expiry.** Pull a warrant, a key, or an agent the moment
+  something looks wrong instead of waiting for the TTL. Revocation lists are
+  published to every verifier.
+- **Central issuance and rotation.** Mint per-job warrants from policy rather
+  than by hand, and rotate root and holder keys on a schedule without
+  touching each agent's environment.
+- **Human approval gates.** Route calls to sensitive tools to a person, so
+  the agent can proceed only with a signed approval.
+- **One searchable audit trail.** Signed receipts from every agent, session,
+  and profile in one place, instead of one `audit.jsonl` per machine.
+
+Tenuo Cloud is the managed version of that control plane. See
+[tenuo.ai](https://tenuo.ai) for access, or the Tenuo repo for running your
+own.
+
+## License
+
+Apache-2.0