toolgate-io 0.3.0__tar.gz

toolgate_io-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,18 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  checks:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+      - run: uv sync --dev
+      - run: uv run ruff check src tests
+      - run: uv run pytest tests/ -q

toolgate_io-0.3.0/.github/workflows/pages.yml

@@ -0,0 +1,30 @@
+name: Deploy portal
+
+on:
+  push:
+    branches: [main]
+    paths: ["site/**"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+      - id: deployment
+        uses: actions/deploy-pages@v4

toolgate_io-0.3.0/.github/workflows/publish.yml

@@ -0,0 +1,22 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # PyPI Trusted Publishing (OIDC) — no stored secrets
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1

toolgate_io-0.3.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+.ruff_cache/
+node_modules/
+dist/
+*.log
+.env
+.env.*
+*.db
+*.db-journal
+*.sqlite
+.DS_Store
+coverage/

toolgate_io-0.3.0/CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing
+
+Thanks for your interest in Toolgate. The project is early and moving fast; this keeps contributions frictionless for everyone.
+
+## Workflow
+
+- **Everything goes through issues and pull requests.** No direct pushes to `main`.
+- Open or claim an issue before large changes — the [issue tracker](../../issues) is the roadmap.
+- Branch from `main`, keep PRs focused, and reference the issue (`Closes #N`).
+- CI must be green: `ruff check` + the full test suite.
+
+## Development setup
+
+```bash
+uv sync
+uv run ruff check src tests
+uv run pytest tests/ -q
+uv run toolgate-demo        # end-to-end sanity
+```
+
+## Ground rules
+
+- **Security-sensitive code** (`toolgate/core/token.py`, `toolgate/core/assertion.py`, `toolgate/core/audit.py`, the gate pipeline) requires tests for every behavior change — including the negative cases (theft, replay, tamper).
+- The wire format (camelCase fields, token claims, endpoints) is a compatibility surface; changes to it need an ADR in `docs/adr/`.
+- New behavior ships with documentation (`docs/`), not just code.
+- No credentials, tokens, or real endpoints in code, tests, fixtures, or issue text — ever.
+
+## Reporting security issues
+
+Do **not** open public issues for exploitable findings — see [SECURITY.md](SECURITY.md).
+
+## License
+
+By contributing you agree that your contributions are licensed under the [Apache License 2.0](LICENSE).

toolgate_io-0.3.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.

toolgate_io-0.3.0/NOTICE

@@ -0,0 +1,4 @@
+Toolgate
+Copyright 2026 Juan Martin Maglione
+
+Licensed under the Apache License, Version 2.0.

toolgate_io-0.3.0/PKG-INFO

@@ -0,0 +1,166 @@
+Metadata-Version: 2.5
+Name: toolgate-io
+Version: 0.3.0
+Summary: Capability control plane for embedded AI agents: scoped tokens, policy enforcement, credential injection, signed audit.
+Project-URL: Homepage, https://maglionejm.github.io/toolgate/
+Project-URL: Documentation, https://github.com/maglionejm/toolgate/blob/main/docs/README.md
+Project-URL: Repository, https://github.com/maglionejm/toolgate
+Project-URL: Issues, https://github.com/maglionejm/toolgate/issues
+Author: Juan Martin Maglione
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ai-agents,audit,capability-tokens,delegation,oauth,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: FastAPI
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Requires-Python: >=3.12
+Requires-Dist: cryptography>=43
+Requires-Dist: fastapi>=0.115
+Requires-Dist: httpx>=0.27
+Requires-Dist: jwcrypto>=1.5.6
+Requires-Dist: pydantic>=2.8
+Requires-Dist: rich>=15.0.0
+Requires-Dist: typer>=0.27.2
+Requires-Dist: uvicorn>=0.30
+Description-Content-Type: text/markdown
+
+# Toolgate
+
+**The capability control plane for embedded AI agents.**
+
+[![CI](https://github.com/maglionejm/toolgate/actions/workflows/ci.yml/badge.svg)](https://github.com/maglionejm/toolgate/actions/workflows/ci.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-c8f169)](LICENSE)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-8b96a1)](pyproject.toml)
+
+**Portal & live simulation: [maglionejm.github.io/toolgate](https://maglionejm.github.io/toolgate/)** — try the gate and tamper with a real hash chain in your browser.
+
+Agents should never hold credentials — not the user's OAuth token, not a tenant API key, not anything. Toolgate sits between agents and the tools they call:
+
+- the agent authenticates with **its own Ed25519 key** and a **delegation grant** from a human;
+- it receives **short-lived capability tokens** (`sub` = the human, `act.sub` = the agent, RFC 8693 semantics) that are useless if stolen (proof-of-possession bound);
+- every tool call is **policy-checked** (allow / deny / require human approval), **metered** against the grant's budget, and executed by the gate, which **injects the real credential server-side**;
+- every decision — including denials — lands in a **hash-chained, Ed25519-signed audit trail**.
+
+```
+Agent (no secrets) ── token + one-time proof ──▶ GATE ── real credential ──▶ Upstream API
+                                                  │
+                                    verify → decide → budget → inject → execute → audit
+```
+
+## Try it
+
+```bash
+uvx --from toolgate-io toolgate demo    # zero-install, straight from PyPI
+```
+
+or from source:
+
+```bash
+uv sync
+uv run toolgate demo
+```
+
+The demo boots Toolgate plus two credential-guarded mock APIs and runs a six-act scenario: an allowed CRM read (the upstream rejects anything without its live key — proving injection), a policy denial, an external email parked for human approval and executed against the approved args only, budget exhaustion, revocation that kills a live token instantly, and audit chain verification with the full decision trace.
+
+```
+[OK      ] read_contact executed -> {'contact': {...}}
+[DENIED  ] TG_DENIED: matched deny rule never-delete
+[PARKED  ] approval apr_... pending — agent is blocked, not trusted
+[HUMAN   ] Sam approved the exact parked arguments (args are hash-bound)
+[OK      ] send_email executed after approval
+[BUDGET  ] blocked: delegation grant budget exhausted
+[REVOKED ] TG_REVOKED: live token died with the grant, no TTL wait
+[AUDIT   ] chain of 10 records — verification: VALID
+```
+
+## How it works
+
+1. **Register** a tenant, its users, agents (public keys only), and upstreams. Upstream credentials are sealed into the vault (AES-256-GCM) and never leave the server.
+2. **Delegate**: a user grants an agent bounded authority — which upstreams/tools (RFC 9396-style `authorization_details`), what budget (cost units), which policy, until when.
+3. **Exchange**: the agent presents a signed client assertion (RFC 7523 style) and receives a capability token — TTL ~2 minutes with jitter, audience-bound, sender-constrained via `cnf.jkt`.
+4. **Call**: each gate call carries the token plus a one-time DPoP-style proof signed by the agent key (bound to method, URL, and token hash; replays rejected).
+5. **Enforce**: token bounds → policy rules (first match wins, glob matching, dot-path argument constraints, cost ceilings) → default deny → atomic budget charge.
+6. **Approve**: `require_approval` parks the call; a human decides on the exact argument set (hash-bound — no post-approval swaps); the agent polls and executes.
+7. **Audit**: every decision appends to a hash chain signed by the gate key. `GET /v1/control/audit/verify` proves nothing was edited, removed, or reordered.
+
+## CLI
+
+Everything an operator does is a `toolgate` command ([full reference](docs/reference/CLI.md)):
+
+```bash
+pip install toolgate-io
+toolgate init                                        # profile + connectivity check
+toolgate keys generate --out agent-key.json          # agent identity (private key stays local)
+toolgate grants create -t tnt_... --user usr_... --agent agt_... \
+    --policy pol_... --budget 100 --authz "crm:*"    # bounded delegation
+toolgate approvals watch -t tnt_... --by usr_...     # interactive human-in-the-loop inbox
+toolgate audit export --out audit.json && toolgate audit verify --file audit.json   # offline proof
+toolgate dev call crm read_contact --grant grt_... --key agent-key.json             # act as the agent
+```
+
+## Agent-side SDK
+
+```python
+from toolgate.sdk import ToolgateClient, PendingApproval, generate_ed25519_key_pair
+
+client = ToolgateClient(
+    base_url=base_url,
+    agent_id=agent_id,
+    agent_private_jwk=agent_private_jwk,  # the only secret an agent ever holds
+    grant_id=grant_id,
+)
+
+result = client.call("crm", "read_contact", {"contactId": "c-001"})
+if isinstance(result, PendingApproval):
+    result = client.wait_for_approval(result.approval_id)
+# Denials, budget exhaustion, and revocation raise typed ToolgateCallError
+# (TG_DENIED / TG_BUDGET_EXCEEDED / TG_REVOKED / TG_PROOF_INVALID / ...).
+```
+
+## Layout
+
+| Module | Purpose |
+| --- | --- |
+| `toolgate.core` | Capability tokens, client assertions + PoP proofs, policy engine, audit chain |
+| `toolgate.server` | Control plane (registry, grants, token endpoint, approvals, revocation, audit) + gate (enforcement pipeline, vault) |
+| `toolgate.sdk` | Agent-side client: token exchange, signed calls, approval flow, typed errors |
+| `toolgate.demo` | End-to-end scenario (`uv run toolgate-demo`) |
+
+## Documentation
+
+Full suite in [`docs/`](docs/README.md): [Quickstart](docs/QUICKSTART.md) · [API Reference](docs/reference/API.md) · [Token Spec](docs/TOKEN-SPEC.md) · [Security Model](docs/SECURITY.md) · [Deployment](docs/DEPLOYMENT.md) · [Operations](docs/OPERATIONS.md)
+
+## Design
+
+- `docs/ARCHITECTURE.md` — components, token design, threat model
+- `docs/adr/0001` — delegation, never user-credential impersonation
+- `docs/adr/0002` — JWT on OAuth rails (RFC 8693/9396/7800) over Biscuit/Macaroon/UCAN
+- `docs/adr/0003` — original TS runtime decision (superseded by 0005)
+- `docs/adr/0004` — approvals bound to args hashes; hash-chained signed audit
+- `docs/adr/0005` — Python as the reference implementation
+
+Roadmap lives in the [issue tracker](../../issues): MCP compatibility, upstream OAuth brokering, Merkle checkpoint anchoring, approvals via Slack/webhooks/CIBA push, dashboard, Postgres scale-out, TypeScript SDK rebuild.
+
+## Development
+
+```bash
+uv sync
+uv run ruff check src tests
+uv run pytest tests/ -q     # 39 tests: core unit + server integration + SDK-vs-server
+uv run toolgate-demo        # the six-act scenario
+uv run toolgate-server      # standalone server (prints the admin key on first boot)
+```
+
+Production env vars: `TOOLGATE_MASTER_KEY`, `TOOLGATE_ADMIN_KEY`, `TOOLGATE_PUBLIC_URL`, `TOOLGATE_DB`, `PORT`.
+
+## Contributing & security
+
+Contributions welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Security findings go through [private vulnerability reporting](SECURITY.md), never public issues.
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 Juan Martin Maglione. Toolgate is early-stage software (pre-1.0): the wire format is a compatibility surface we take seriously, but expect movement before 1.0.

toolgate_io-0.3.0/README.md

@@ -0,0 +1,136 @@
+# Toolgate
+
+**The capability control plane for embedded AI agents.**
+
+[![CI](https://github.com/maglionejm/toolgate/actions/workflows/ci.yml/badge.svg)](https://github.com/maglionejm/toolgate/actions/workflows/ci.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-c8f169)](LICENSE)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-8b96a1)](pyproject.toml)
+
+**Portal & live simulation: [maglionejm.github.io/toolgate](https://maglionejm.github.io/toolgate/)** — try the gate and tamper with a real hash chain in your browser.
+
+Agents should never hold credentials — not the user's OAuth token, not a tenant API key, not anything. Toolgate sits between agents and the tools they call:
+
+- the agent authenticates with **its own Ed25519 key** and a **delegation grant** from a human;
+- it receives **short-lived capability tokens** (`sub` = the human, `act.sub` = the agent, RFC 8693 semantics) that are useless if stolen (proof-of-possession bound);
+- every tool call is **policy-checked** (allow / deny / require human approval), **metered** against the grant's budget, and executed by the gate, which **injects the real credential server-side**;
+- every decision — including denials — lands in a **hash-chained, Ed25519-signed audit trail**.
+
+```
+Agent (no secrets) ── token + one-time proof ──▶ GATE ── real credential ──▶ Upstream API
+                                                  │
+                                    verify → decide → budget → inject → execute → audit
+```
+
+## Try it
+
+```bash
+uvx --from toolgate-io toolgate demo    # zero-install, straight from PyPI
+```
+
+or from source:
+
+```bash
+uv sync
+uv run toolgate demo
+```
+
+The demo boots Toolgate plus two credential-guarded mock APIs and runs a six-act scenario: an allowed CRM read (the upstream rejects anything without its live key — proving injection), a policy denial, an external email parked for human approval and executed against the approved args only, budget exhaustion, revocation that kills a live token instantly, and audit chain verification with the full decision trace.
+
+```
+[OK      ] read_contact executed -> {'contact': {...}}
+[DENIED  ] TG_DENIED: matched deny rule never-delete
+[PARKED  ] approval apr_... pending — agent is blocked, not trusted
+[HUMAN   ] Sam approved the exact parked arguments (args are hash-bound)
+[OK      ] send_email executed after approval
+[BUDGET  ] blocked: delegation grant budget exhausted
+[REVOKED ] TG_REVOKED: live token died with the grant, no TTL wait
+[AUDIT   ] chain of 10 records — verification: VALID
+```
+
+## How it works
+
+1. **Register** a tenant, its users, agents (public keys only), and upstreams. Upstream credentials are sealed into the vault (AES-256-GCM) and never leave the server.
+2. **Delegate**: a user grants an agent bounded authority — which upstreams/tools (RFC 9396-style `authorization_details`), what budget (cost units), which policy, until when.
+3. **Exchange**: the agent presents a signed client assertion (RFC 7523 style) and receives a capability token — TTL ~2 minutes with jitter, audience-bound, sender-constrained via `cnf.jkt`.
+4. **Call**: each gate call carries the token plus a one-time DPoP-style proof signed by the agent key (bound to method, URL, and token hash; replays rejected).
+5. **Enforce**: token bounds → policy rules (first match wins, glob matching, dot-path argument constraints, cost ceilings) → default deny → atomic budget charge.
+6. **Approve**: `require_approval` parks the call; a human decides on the exact argument set (hash-bound — no post-approval swaps); the agent polls and executes.
+7. **Audit**: every decision appends to a hash chain signed by the gate key. `GET /v1/control/audit/verify` proves nothing was edited, removed, or reordered.
+
+## CLI
+
+Everything an operator does is a `toolgate` command ([full reference](docs/reference/CLI.md)):
+
+```bash
+pip install toolgate-io
+toolgate init                                        # profile + connectivity check
+toolgate keys generate --out agent-key.json          # agent identity (private key stays local)
+toolgate grants create -t tnt_... --user usr_... --agent agt_... \
+    --policy pol_... --budget 100 --authz "crm:*"    # bounded delegation
+toolgate approvals watch -t tnt_... --by usr_...     # interactive human-in-the-loop inbox
+toolgate audit export --out audit.json && toolgate audit verify --file audit.json   # offline proof
+toolgate dev call crm read_contact --grant grt_... --key agent-key.json             # act as the agent
+```
+
+## Agent-side SDK
+
+```python
+from toolgate.sdk import ToolgateClient, PendingApproval, generate_ed25519_key_pair
+
+client = ToolgateClient(
+    base_url=base_url,
+    agent_id=agent_id,
+    agent_private_jwk=agent_private_jwk,  # the only secret an agent ever holds
+    grant_id=grant_id,
+)
+
+result = client.call("crm", "read_contact", {"contactId": "c-001"})
+if isinstance(result, PendingApproval):
+    result = client.wait_for_approval(result.approval_id)
+# Denials, budget exhaustion, and revocation raise typed ToolgateCallError
+# (TG_DENIED / TG_BUDGET_EXCEEDED / TG_REVOKED / TG_PROOF_INVALID / ...).
+```
+
+## Layout
+
+| Module | Purpose |
+| --- | --- |
+| `toolgate.core` | Capability tokens, client assertions + PoP proofs, policy engine, audit chain |
+| `toolgate.server` | Control plane (registry, grants, token endpoint, approvals, revocation, audit) + gate (enforcement pipeline, vault) |
+| `toolgate.sdk` | Agent-side client: token exchange, signed calls, approval flow, typed errors |
+| `toolgate.demo` | End-to-end scenario (`uv run toolgate-demo`) |
+
+## Documentation
+
+Full suite in [`docs/`](docs/README.md): [Quickstart](docs/QUICKSTART.md) · [API Reference](docs/reference/API.md) · [Token Spec](docs/TOKEN-SPEC.md) · [Security Model](docs/SECURITY.md) · [Deployment](docs/DEPLOYMENT.md) · [Operations](docs/OPERATIONS.md)
+
+## Design
+
+- `docs/ARCHITECTURE.md` — components, token design, threat model
+- `docs/adr/0001` — delegation, never user-credential impersonation
+- `docs/adr/0002` — JWT on OAuth rails (RFC 8693/9396/7800) over Biscuit/Macaroon/UCAN
+- `docs/adr/0003` — original TS runtime decision (superseded by 0005)
+- `docs/adr/0004` — approvals bound to args hashes; hash-chained signed audit
+- `docs/adr/0005` — Python as the reference implementation
+
+Roadmap lives in the [issue tracker](../../issues): MCP compatibility, upstream OAuth brokering, Merkle checkpoint anchoring, approvals via Slack/webhooks/CIBA push, dashboard, Postgres scale-out, TypeScript SDK rebuild.
+
+## Development
+
+```bash
+uv sync
+uv run ruff check src tests
+uv run pytest tests/ -q     # 39 tests: core unit + server integration + SDK-vs-server
+uv run toolgate-demo        # the six-act scenario
+uv run toolgate-server      # standalone server (prints the admin key on first boot)
+```
+
+Production env vars: `TOOLGATE_MASTER_KEY`, `TOOLGATE_ADMIN_KEY`, `TOOLGATE_PUBLIC_URL`, `TOOLGATE_DB`, `PORT`.
+
+## Contributing & security
+
+Contributions welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Security findings go through [private vulnerability reporting](SECURITY.md), never public issues.
+
+## License
+
+[Apache License 2.0](LICENSE) © 2026 Juan Martin Maglione. Toolgate is early-stage software (pre-1.0): the wire format is a compatibility surface we take seriously, but expect movement before 1.0.

toolgate_io-0.3.0/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+Toolgate is security infrastructure: reports are taken seriously and handled with priority.
+
+## Reporting a vulnerability
+
+- **Please do not open a public issue for exploitable findings.**
+- Use GitHub's [private vulnerability reporting](../../security/advisories/new) on this repository.
+- Include: affected component, reproduction steps, and impact assessment. Proof-of-concept code is welcome.
+- You will receive an acknowledgement within 72 hours.
+
+## Scope of interest
+
+Highest-value targets, in order:
+
+1. The proof-of-possession layer (`toolgate/core/assertion.py`) — hand-implemented (no maintained Python DPoP library exists); theft, replay, downgrade, and confusion attacks especially welcome.
+2. Token verification and claim enforcement (`toolgate/core/token.py`, gate pipeline).
+3. Audit-chain integrity (`toolgate/core/audit.py`) — any way to alter history that verification does not detect.
+4. Policy-engine bypasses (glob/constraint edge cases, tool resolution).
+5. Vault handling and credential-leak paths.
+
+## Current status
+
+Pre-1.0. The threat model, guarantees, and **known gaps** are documented honestly in [docs/SECURITY.md](docs/SECURITY.md) — please read it before reporting items already listed there (admin-plane hardening, external audit anchoring, and KMS envelope encryption are known and tracked).