gargoyle-receipts 0.4.0.dev0__tar.gz

gargoyle_receipts-0.4.0.dev0/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.

gargoyle_receipts-0.4.0.dev0/NOTICE

@@ -0,0 +1,6 @@
+Gargoyle
+Copyright 2026 Justin LaPorte
+
+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

gargoyle_receipts-0.4.0.dev0/PKG-INFO

@@ -0,0 +1,361 @@
+Metadata-Version: 2.4
+Name: gargoyle-receipts
+Version: 0.4.0.dev0
+Summary: Signed, single-use, argument-bound receipts and human-approval holds for agent tool calls.
+Author: Justin LaPorte
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Elyon-Sol/Gargoyle
+Project-URL: Source, https://github.com/Elyon-Sol/Gargoyle
+Project-URL: Specification, https://github.com/Elyon-Sol/Gargoyle/blob/main/SPEC.md
+Project-URL: Issues, https://github.com/Elyon-Sol/Gargoyle/issues
+Keywords: agents,mcp,authorization,receipts,ed25519,human-in-the-loop
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography>=44.0.0
+Requires-Dist: fastapi>=0.115
+Requires-Dist: uvicorn>=0.30
+Requires-Dist: requests>=2.32
+Provides-Extra: redis
+Requires-Dist: redis; extra == "redis"
+Provides-Extra: dev
+Requires-Dist: httpx>=0.27; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: redis; extra == "dev"
+Dynamic: license-file
+
+# Gargoyle
+
+Signed, single-use, argument-bound receipts and human-approval holds for
+agent tool calls.
+
+An agent asks for permission to run a tool. Something you already trust
+decides (OPA, Cedar, your own code). Gargoyle turns that decision into a
+**receipt**: an Ed25519-signed record that names the tool, a hash of its
+arguments, the principal the decision was made for, the target it may be
+presented to, and the policy that decided. The target checks the receipt
+before it acts, and honors it once. When the policy says a call needs a
+human, the receipt is held until an approver signs a **grant** for exactly
+that decision with a key the issuing service does not have.
+
+Gargoyle does not decide whether a call is allowed. It makes an allow
+decision portable, verifiable, bound to one call by one caller, and
+spendable once. The decision comes from your policy engine (an OPA adapter
+is included); the caller is authenticated by your transport (the
+proxy-verified client certificate, by default); Gargoyle sits in front of
+your MCP server and lets through only what both agreed to.
+
+Status: pre-release (`0.4.0.dev0`). The wire format is `gargoyle/3` and may
+still change before the first release; it is specified in [SPEC.md](SPEC.md).
+
+## What a receipt gives you
+
+- **Binding.** A receipt for `transfer_funds` with `{"amount": 250}` is
+  refused for `{"amount": 250000}`, for `delete_database`, and at any
+  target but the one it names.
+- **A principal.** The receipt carries the identity the issuer
+  authenticated; the target compares it with the identity it authenticated.
+  A receipt obtained by one agent cannot be spent by another. When the agent
+  acts for a user, the receipt records that too (`on_behalf_of`).
+- **Standard encodings.** A receipt can travel as a JWS (EdDSA) that any
+  JWT library verifies, and the issuer can take the caller's identity from
+  an OAuth bearer token, an RFC 8693 delegation token or a Transaction
+  Token, signed EdDSA, RS256 or ES256 by keys from the provider's JWKS.
+  With Entra ID the principal is the user's UPN and the token's groups and
+  app roles become policy inputs, so a rules file can say "finance may hold
+  invoice updates; shipping may not" without naming people.
+- **Single use.** Every receipt carries a signed `decision_id`; an executor
+  claims it exactly once. A replayed receipt is refused.
+- **Expiry.** Every receipt carries a signed `not_after` (default 300 s). A
+  captured receipt, or a leaked issuer key, is useful for minutes, not
+  forever.
+- **Currency.** The receipt pins the policy that decided. If the policy
+  changes, outstanding receipts stop being honored and the call must be
+  decided again.
+- **Holds.** A decision that requires approval is flagged inside the signed
+  receipt. The target will not run it without a grant a human signed for
+  that exact decision, under their own key, on their own device.
+- **Proof of execution.** An executor with a key answers each honored call
+  with a signed execution receipt: the decision it fulfilled, the policy
+  version that allowed it, and a hash of the outputs. Receipt, grant and
+  execution receipt verify together, offline, with three public keys.
+
+## Install
+
+    pip install -e ".[dev]"
+    python -m pytest
+
+Python 3.12 or later. A TypeScript verifier and consumer for Node 20+
+lives in [ts/](ts/) (`cd ts && npm install && npm test`); its suite
+recomputes the same conformance vectors byte for byte, so the two
+implementations cannot drift apart silently. Redis is optional (`.[redis]`) and only needed to
+share the replay cache and pending-approval set across executor replicas.
+
+## Issuing a receipt
+
+The policy is anything with `pin()` and `decide()`; see `gargoyle.policy`.
+The interaction you pass carries the call (`tool`, `args`, `principal`) and
+whatever claims your policy reads. The receipt records only the call and
+the policy pin.
+
+```python
+from gargoyle.issuer import ENVELOPE_HEADER, issue
+
+who = principal_from_token(bearer_or_transaction_token, IDP_KEYS, audience="issuer")  # gargoyle.identity
+# IDP_KEYS: pinned, or entra_keys("<tenant>") / keys_from_jwks(<provider JWKS>)
+interaction = {
+    "tool": "transfer_funds",
+    "args": {"amount": 250, "to": "acct-9"},
+    "principal": who["principal"],         # the agent, as the identity provider authenticated it
+    "on_behalf_of": who["on_behalf_of"],   # the user it acts for, when the token says so
+    **claims,                              # whatever your policy decides on
+}
+result = issue(policy, "https://tools.example.com/target", interaction,
+               signing_key=issuer_private_key, key_id="issuer-2026-10")
+
+if result.envelope is None:
+    refuse(result.decision.reason)
+elif result.decision.requires_approval:
+    hold(result.envelope)            # see "Approval holds"
+else:
+    send(call, headers={ENVELOPE_HEADER: json.dumps(result.envelope)})
+    # or, for a target that speaks JWT: gargoyle.jws.encode_receipt(result.envelope, issuer_private_key)
+```
+
+**Open Policy Agent.** `gargoyle.opa.OpaPolicy` asks OPA's data API and
+pins the exact set of policy modules OPA holds, so editing a policy
+invalidates every outstanding receipt until the call is decided again.
+
+```python
+from gargoyle.opa import OpaPolicy
+policy = OpaPolicy("http://127.0.0.1:8181", "gargoyle/decision")
+```
+
+```rego
+package gargoyle
+default decision := {"allow": false, "reason": "DEFAULT_DENY"}
+decision := {"allow": true, "requires_approval": input.tool == "transfer_funds"} {
+    input.principal == "spiffe://example.org/agents/payments"
+    input.tool in {"read_balance", "transfer_funds"}
+}
+```
+
+OPA unreachable, an undefined document, or a result in no recognized shape
+is a refusal, never an issuance. Any other engine goes behind the same
+two-method interface.
+
+**No engine.** `gargoyle.rules.RulesPolicy` decides from a JSON file:
+first matching rule wins, globs on tool name, principal, delegation,
+the caller's groups and roles, and string arguments, actions allow, hold
+or deny. The pin is the file's hash,
+so an edit invalidates outstanding receipts exactly as an engine change
+does. This is what `gargoyle init` sets up.
+
+## Checking a receipt
+
+Every executor runs the same check: establish the live policy pin,
+establish the trusted issuer keys, verify the receipt against the call it is
+about to run, claim the `decision_id`. `gargoyle.consumer.Consumer` packages
+it.
+
+```python
+from gargoyle.consumer import Consumer
+
+consumer = Consumer(
+    target_id="https://tools.example.com/target",
+    pinned_public_keys={"issuer-2026-10": issuer_public_key},
+    record_bytes=open("published_record.json", "rb").read(),   # {policy_id, policy_sha256}
+)
+
+call = {"tool": name, "args": arguments, "principal": peer_identity}
+verdict = consumer.check(envelope, call)
+if verdict.honored:
+    run(name, arguments)
+else:
+    refuse(verdict.reason)           # REF_VERIFY_* or REF_TARGET_*
+```
+
+`peer_identity` is who *you* authenticated as the caller (an mTLS peer, a
+bearer token's subject, an identity a trusted proxy asserted). It is never
+read from the request. A consumer refuses to be built without issuer-key
+trust, and the verifier refuses to run without it, so an unsigned receipt is
+never honored. For a flagged receipt, pass the human's grant as
+`grant=`; the consumer verifies it against the receipt's own decision and
+hold, claims it once, and only then claims the receipt.
+
+For a live pin that can be reissued, give the consumer a record source
+(a publisher-signed record with a serial and an expiry) instead of a
+static pin; for issuer keys that can be rotated and revoked, a key record
+source. Both are consulted on every check and fail closed.
+
+## Proof that it ran
+
+Give a consumer an executor key and it signs an execution receipt after the
+side effect. Anyone holding the issuer's, approver's and executor's public
+keys can then audit one call with no network and no live state:
+
+```python
+from gargoyle.execution import verify_chain
+
+chain = verify_chain(receipt, execution,
+                     issuer_public_keys=ISSUER_KEYS, executor_public_keys=EXECUTOR_KEYS,
+                     grant=grant, approver_public_keys=APPROVER_KEYS,
+                     outputs=outputs, check_outputs=True)
+chain["accepted"], chain["steps"]   # True, [("authorization", ...), ("approval", ...), ("execution", ...)]
+```
+
+That is the sentence Gargoyle can say that nobody else can: a specific
+policy version authorized a specific call for a specific principal, a
+human's key released it, and exactly that call ran once, verifiable offline
+by anyone, in Python or TypeScript.
+
+The MCP middleware also keeps an evidence log: one hash-chained line per
+decision, refusals and declined holds included, so the trail answers "what
+did the agent try" as well as "what did it do". `gargoyle audit --log`
+verifies every entry and the chain, and prints the tail hash to note down
+so a later copy that lost its end is caught (SPEC.md section 15).
+
+## Where it sits
+
+MCP gateways (TrueFoundry, Monosign, hoop.dev, Akto and others) hold a
+tool call, notify a reviewer and log the click. Gargoyle is not a gateway.
+It runs beside the client, and its approval is a signature made with a key
+the issuer never holds, checked at execution and again by anyone later. In
+2026 three Internet-Drafts describe parts of the same shape: Acta signed
+receipts (an access decision, signed), EP authorization receipts (a human's
+pre-execution signoff), XAIP receipts (a signed execution record). Gargoyle
+chains all three on one decision id with the policy version inside, uses
+the same RFC 8785 canonical form they do, and SPEC.md section 16 maps every
+field. A hold can also be announced to Slack or any webhook
+(`GARGOYLE_HOLD_WEBHOOK_URL`); the notice carries no key, so nothing in a
+chat channel can approve anything.
+
+## Deploy it
+
+Three commands, no policy engine, no containers, no client changes:
+
+    gargoyle init /path/the/agent/may/touch     # keys, config, rules.json
+    gargoyle issuer                             # the issuing service, on rules.json
+    gargoyle approve --watch 2                  # where the approver sits (terminal)
+
+or approve in a browser: open the issuer's `/approve` page and load
+`approver-web.json`; the page shows each held call with its full arguments,
+checked against the receipt, and signs the grant locally with WebCrypto.
+The key never leaves the browser. Then paste the server entry from
+`gargoyle-deploy/mcp-config.json` into your MCP client.
+[docs/guide-hyperv-ubuntu-apache.md](docs/guide-hyperv-ubuntu-apache.md)
+is the full single-instance build: Ubuntu VM on Hyper-V, Apache with TLS,
+a Windows 11 client running Claude Code. Reads are free, writes block until the approver's key
+signs, deletes are refused; the policy is a JSON rules file you edit. A
+hold can demand more than one signature: `"approvals": 2` on a rule, with
+an optional `"approvers": [...]` naming which keys count, puts the terms
+in the receipt itself, and `gargoyle init --approvers 2` creates the keys.
+Every honored call comes back with receipt, grants and execution receipt,
+and `gargoyle audit` verifies them later offline.
+[examples/filesystem-agent](examples/filesystem-agent/) walks through it,
+and through the alternative with OPA in Docker for sites that run a policy
+engine.
+
+## The shipped consumer
+
+**MCP middleware** (`python -m gargoyle.mcp_server -- <upstream command>`):
+a stdio MCP server you put in front of any other stdio MCP server. The
+handshake, `tools/list` and everything else are relayed. A `tools/call` is
+forwarded only when `params._meta["gargoyle/envelope"]` carries a valid
+receipt for that tool, those arguments and the principal the server serves
+(and `params._meta["gargoyle/grant"]` a grant, when the receipt is
+flagged); a refused call is answered here and never reaches the upstream.
+Without an upstream command it runs a built-in demo executor. With
+`GARGOYLE_MCP_ISSUER_URL` and `GARGOYLE_MCP_CLIENT_TOKEN` it obtains a
+receipt from the issuing service for any call that carries none, and
+waits for the human's grant when the call is flagged, so clients that
+cannot attach receipts work unchanged. Configuration is by environment:
+
+| Variable | Meaning |
+|---|---|
+| `GARGOYLE_MCP_GATE_KEY_ID`, `GARGOYLE_MCP_GATE_PUBLIC_KEY_HEX` | the pinned issuer key |
+| `GARGOYLE_MCP_TARGET_ID` | the target identity receipts bind to |
+| `GARGOYLE_MCP_PRINCIPAL` | the client this server serves |
+| `GARGOYLE_MCP_RECORD_PATH` | the published policy record |
+| `GARGOYLE_MCP_APPROVER_KEY_ID`, `GARGOYLE_MCP_APPROVER_PUBLIC_KEY_HEX` | the approver keys whose grants release flagged calls (optional, both or neither; comma-separated lists for several) |
+| `GARGOYLE_MCP_EXECUTOR_KEY_ID`, `GARGOYLE_MCP_EXECUTOR_KEY_HEX` | this server's own signing key, so honored calls carry an execution receipt in `_meta["gargoyle/execution"]` (optional, both or neither) |
+| `GARGOYLE_MCP_ISSUER_URL`, `GARGOYLE_MCP_CLIENT_TOKEN` | self-issue mode: the issuing service and the identity token (whose subject is this server's principal) to obtain receipts with; `GARGOYLE_MCP_APPROVAL_TIMEOUT_SECONDS` and `GARGOYLE_MCP_POLL_SECONDS` tune the wait for a grant |
+| `GARGOYLE_HOLD_WEBHOOK_URL`, `GARGOYLE_APPROVE_URL` | issuer: POST a notice of every new hold (Slack incoming-webhook shape, `text` plus the hold) with a link to the console; notice only, the grant still needs the approver's key |
+| `GARGOYLE_MCP_AUDIT_LOG` | the evidence log: every decision, honored or refused, as one hash-chained JSON line with its receipt, grant and execution receipt; `gargoyle audit --log` verifies the file |
+
+**Issuing service** (`gargoyle.issuer_service`, run with uvicorn from
+`app_from_env()`): identity token in, receipt out, with the hold and grant
+exchange for flagged calls (`/issue`, `/pending`, `/grants`, `/decline`,
+`/record`, `/keys`) and the browser approval console at `/approve`. Policy
+from a rules file or OPA; identity from a pinned key or, with
+`GARGOYLE_ENTRA_TENANT`, the tenant's signing keys.
+
+
+## Approval holds
+
+When the policy's decision carries `requires_approval`, the receipt is
+issued with `requires_approval: true` and a signed `approval_request_id`.
+No target will run it on its own: the consumer demands a grant for exactly
+that decision and hold, verifies it (provenance, separation of duties,
+binding, expiry), claims it once, and only then claims the receipt. A human
+runs `gargoyle-approver` on a machine that holds the approver private key;
+given the receipt it shows the tool, argument hash, principal, target and
+policy that are inside the issuer's signature, and emits the grant. The
+agent presents receipt and grant together. Approver keys should come from a
+signed key record where the key's role is `approver`
+(`gargoyle.approver_trust`), so an issuer-controlled key can never approve.
+An issuer that prefers to hold flagged receipts until the grant exists can
+do that too (`gargoyle.pending_store`); the target's check does not depend
+on it.
+
+## Modules
+
+| Module | Role |
+|---|---|
+| `policy` | the decision interface |
+| `opa` | the Open Policy Agent adapter |
+| `rules` | a policy from a JSON rules file, for sites without an engine |
+| `cli` | the `gargoyle` command: init, issuer, approve, audit |
+| `issuer` | ask the policy, sign the receipt |
+| `identity` | the issuer's identity input: bearer, delegation and transaction tokens to principal and on_behalf_of |
+| `jws` | the receipt as a JWS any JWT library verifies |
+| `envelope` | receipt construction, hash region, signature region, currency check |
+| `verifier` | the pure target-side check and every refusal code |
+| `consumer` | `Consumer` (pin, keys, verify, claim, attest) and the reference HTTP target |
+| `execution` | execution receipts and the offline chain check |
+| `evidence` | the executor's hash-chained log of every decision, and its offline verifier |
+| `mcp_server` | the stdio MCP middleware (and demo executor), with self-issue mode |
+| `fs_server` | a small Python filesystem MCP server, for clients without Node |
+| `issuer_service` | the HTTP issuing service: identity in, receipts out, holds and grants |
+| `replay_cache`, `pending_store` | single use for receipts and holds; in-memory or Redis |
+| `approval`, `approver_cli`, `approver_trust` | grants, the human's tool, approver key trust |
+| `published_record_source` | the live policy pin as a publisher-signed record with serial and expiry |
+| `key_record_source` | root-signed issuer and approver keys with windows and revocation |
+
+## What Gargoyle does not do
+
+- It does not decide. The policy does, and the receipt is only as good as
+  that decision.
+- It does not authenticate principals. The issuer and the target each
+  authenticate the caller themselves (by default, the target trusts the
+  client certificate its proxy verified); Gargoyle compares the two results.
+- It cannot stop a caller that never asks for a receipt. Only a target that
+  refuses unattested calls can.
+- It does not distribute trust material. Issuer keys, record files, root
+  keys and the client token are the deployer's to protect.
+- The approval flow separates duties only if the approver's private key is
+  out of the issuing service's reach. That is a deployment property.
+
+## License
+
+Apache License 2.0; see [LICENSE](LICENSE) and [NOTICE](NOTICE).