ica-capture 0.1.0__tar.gz

ica_capture-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 [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.

ica_capture-0.1.0/PKG-INFO

@@ -0,0 +1,226 @@
+Metadata-Version: 2.4
+Name: ica-capture
+Version: 0.1.0
+Summary: Emit AI agent steps to ICA. ICA signs and governs them. A tool guard, tool hooks, a callback recorder and an approval pause for agent frameworks (the framework is a setting), MCP, plus outside eval intake.
+Author: ALEETH
+License: Apache-2.0
+Project-URL: Homepage, https://aleeth.com
+Keywords: ai,agents,governance,audit,approvals,tool-guard,mcp,evals,ica
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: callbacks
+Requires-Dist: langchain-core>=0.2; extra == "callbacks"
+Dynamic: license-file
+
+# ICA Capture SDK (Python)
+
+Emit your AI agent's steps to ICA in one line. ICA does the rest: it mints a
+signed, append-only receipt for every step, scores the run into continuous
+posture, and can halt an agent that crosses a control. You sign nothing and hold
+no key.
+
+A receipt of what ran is the floor. ICA also decides what is allowed to run: a
+gated call waits for ICA's decision before the tool body executes, a call held
+for people waits for their approval, and an agent that crosses a control can be
+halted. Each decision ICA seals carries a signed receipt that anyone can
+re-check later.
+
+## Install
+
+```bash
+pip install ica-capture            # core, zero dependencies
+pip install "ica-capture[callbacks]"   # adds the framework callback recorder
+```
+
+## Configure
+
+```python
+from ica import IcaClient
+
+ica = IcaClient(
+    token="YOUR_ICA_INGEST_TOKEN",   # X-ICA-Ingest-Token
+    agent_handle="your-agent",        # resolves to your registered identity
+)
+```
+
+Your ingest credential names your tenant, so `customer_id` is optional. If you
+pass it, it must be the same tenant: ICA refuses any other (403
+`ingest_tenant_mismatch`).
+
+Telemetry never breaks your agent. Emit failures are swallowed by default; pass
+`raise_on_error=True` while you are wiring things up.
+
+## Three drop-in surfaces
+
+### Callback recorder (one line)
+
+```python
+from ica.callbacks import IcaCallbackHandler
+
+agent.invoke(payload, config={"callbacks": [IcaCallbackHandler(ica)]})
+```
+
+Every tool call, ok or error, is recorded with timing, through the agent framework's own callback surface
+(install the `[callbacks]` extra).
+
+### Decorator
+
+```python
+from ica import ica_tool
+
+@ica_tool(ica, reversibility_tag="reversible")
+def search(query):
+    ...
+```
+
+### MCP or any callable
+
+```python
+from ica import wrap_mcp_tool
+
+guarded = wrap_mcp_tool(ica, raw_tool_call, name="filesystem.read")
+```
+
+### Manual
+
+```python
+ica.record_tool_call(
+    tool_name="web.search",
+    tool_input={"query": "..."},
+    tool_output={"hits": 3},
+    duration_ms=142,
+)
+```
+
+## What ICA does with it
+
+Each step posts to `POST /api/ingest/agent-step`. On arrival ICA:
+
+1. Mints an L7 receipt over the step, signed server-side. You never touch a key.
+2. Appends it to an append-only, tamper-evident audit trail.
+3. Feeds it to the assessment engine: decision control, containment,
+   reversibility, observability, continuous posture.
+4. Enforces. A step that bypasses a gate or runs an irreversible action ungated
+   is flagged, and a halted agent is quarantined at ingest.
+
+Verify any receipt without publishing your data. Public chains are optional, not
+required, and never the default.
+
+## Step fields
+
+| Field | Notes |
+|-------|-------|
+| `step_type` | `reasoning`, `tool_call`, `sub_agent_dispatch`, `final_answer`, `gate_request`, `gate_response` |
+| `tool_name` | the tool invoked |
+| `tool_input` / `tool_output` | JSON-safe; coerced if needed |
+| `reversibility_tag` | `reversible`, `partial`, `irreversible`, `unclassified` |
+| `gate_state` | `not_gated`, `pending`, `approved`, `denied`, `bypassed` |
+| `duration_ms`, `tokens_used` | optional metrics |
+
+## Tool guard and tool hooks
+
+For a graph whose held calls should wait for people, use `ica.approval_pause` (below): a held call pauses the
+graph instead of ending it, and the block is hard. The callback recorder above still records graph runs. Two
+more, neither of which adds a dependency. The agent framework is a setting, never a module name:
+
+| Use | `framework=` | Hard block with `gate=True` |
+|---|---|---|
+| `from ica.tool_guard import guard_tools`; `tools = guard_tools(ica, tools, framework=..., gate=True)` | `"openai_agents"` | yes: wraps each dataclass function tool's `on_invoke_tool` |
+| the same | `"crewai"` | yes: wraps each tool's `_run` |
+| the same | `"llamaindex"` | yes: wraps `FunctionTool` `_fn` and `_async_fn` |
+| `from ica.tool_hooks import IcaHooks`; `Agent(tools=..., hooks=[IcaHooks(ica, gate=True)])` | (frameworks that call tool hooks) | yes: a deny sets `cancel_tool` |
+
+An unknown `framework=` raises `ValueError`, so a typo never leaves tools unguarded. A tool of another shape is
+returned unchanged.
+
+## Stated confidence
+
+An agent can tell ICA how sure it is of each gated call, as a number from 0 to 1. When the agent's scope
+contract sets a confidence floor (`operating_envelope.confidence_floor`), ICA holds a call below the floor,
+or one that states nothing, for a person: `gate()` answers `pending` and the tool does not run. A high
+number never loosens anything; every other check still decides.
+
+- `ica.gate(action, tool_name=..., stated_confidence=0.82)` sends it on one call.
+- Every adapter and decorator takes `confidence=`: a number, or a function `(tool_name, payload) -> number`
+  that reads the model's own statement (for example a `confidence` field your tool schema asks the model to
+  fill). A function that raises states nothing, so with a floor set the call is held.
+
+```python
+tools = guard_tools(ica, tools, framework="crewai", gate=True, confidence=lambda name, payload: payload.get("kwargs", {}).get("confidence"))
+```
+
+## Approval pause: a held call pauses the graph
+
+Every other adapter treats a call ICA holds for a person (`pending`) as a deny: the run ends. In a graph runtime
+with `interrupt()` and a checkpointer the graph can wait instead.
+
+```python
+from langchain_core.tools import tool
+from langgraph.checkpoint.memory import MemorySaver
+from langgraph.prebuilt import ToolNode
+from ica.approval_pause import ica_approval_pause_tool, route_tool_calls
+
+@tool
+@ica_approval_pause_tool(ica, reversibility_tag="irreversible")
+def update_claim(claim_id: int, amount: int) -> str:
+    ...
+
+builder.add_node("tools", ToolNode([update_claim]))
+builder.add_conditional_edges("agent", route_tool_calls, ["tools", END])   # one task per tool call
+graph = builder.compile(checkpointer=MemorySaver())                       # pausing needs a checkpointer
+```
+
+- Approved: the tool runs and its step carries the single-use token. Denied: `GateDenied`, the tool never runs.
+- Held: ICA raises a two-person approval request bound to the exact arguments, and the graph pauses
+  (`interrupt()`); the payload carries `approval_request_id`. Two named people approve it in the ICA console.
+  Resume with `Command(resume=...)` (one value per pending interrupt when several pause at once). The resume
+  value is only a wake-up: the tool asks ICA, and runs only when ICA releases a token for that call. Still
+  pending, or ICA briefly unreachable: it pauses again. Denied, expired, arguments changed, or the agent halted,
+  retired or cert-blocked since the approval: `GateDenied`. Already released (a re-run after it ran): it does
+  not run again and returns a message saying so.
+- One tool call per task. A resumed graph task runs again from the top, and a plain `ToolNode` wired on the
+  messages list runs every call of a turn in one task, so the other calls of that turn would run again when one
+  pauses. Use `route_tool_calls` (above) or `create_react_agent` (its default version "v2" already sends each
+  call on its own). Tested with the graph runtime package at 1.2.14 (tests/test_approval_pause_real.py): with the routing, an approved call beside a held one runs once;
+  without it, twice.
+- Needs a per-customer ingest credential: only the credential that raised a request can collect it, and a
+  shared token raises none. A tenant that approves with one person gets no request either: this path releases
+  only on two named approvals. Outside a graph run nothing is requested and a hold ends the call, as before.
+- A request waits up to an hour for a person, an approval must be collected within an hour of being given, and a
+  credential can have at most 25 requests waiting. Arguments holding an integer past 2^53 are refused (JSON cannot
+  carry it exactly): send such ids as strings.
+- Each resume re-asks the gate (one more sealed `pending` decision). A `hold_key` derived from the thread and
+  task makes the re-ask find the same request. Pass `key_fn=` to name calls yourself.
+- Under it: `ica.gate(..., request_approval=True, args=..., hold_key=...)` and `ica.release(approval_request_id,
+  args)`, which any framework can use.
+
+## Signed proof in your agent's trace
+
+Every gate decision ICA seals comes back with its signed receipt. Give the client an `on_proof` function and that proof lands
+in your agent's own trace, beside the tool call it decided:
+
+```python
+ica = IcaClient(token="...", agent_handle="pay-bot", on_proof=add_to_current_run)
+```
+
+`add_to_current_run(proof)` is yours: add the dict to the current run's metadata in whatever tracing tool you use. The dict
+is flat strings: `ica_receipt_hash`, `ica_verify_url`, `ica_decision`, `ica_gate_id`, `ica_signing_key_id`, `ica_tool`.
+Anyone holding the hash re-checks the decision at the verify URL (public, no sign-in) or offline against ICA's published
+keys, without trusting your tracer or ALEETH. Every adapter above that gates (`gate=True`, the tool guard, the tool hooks,
+the approval pause) goes through `gate()`, so it carries the proof; the same dict is on the verdict as `verdict["proof"]`,
+and `proof_of(verdict)` builds it from any gate answer. A decision ICA could not seal gives no proof. A function that raises
+never changes the decision (it raises only with `raise_on_error=True`). A step recorded without a gate is signed just after
+ICA answers, so its receipt is not in that answer.
+
+## Outside eval results
+
+`from ica.evals import record_eval`, then `record_eval(ica, result, framework="ragas", run_name=..., thresholds={...})`.
+Reads Ragas, DeepEval, Giskard, TruLens, promptfoo and plain `{metric: score}` results, and files the
+summary (per-metric mean, min, max, count, pass and fail counts, failed thresholds, never the eval's
+prompts or answers) as one step on the agent's ICA record, where it is sealed like every other step.
+
+## License
+
+This SDK is licensed under the Apache License 2.0 (see LICENSE). Using ICA needs an ingest token: contact ALEETH
+(https://aleeth.com).

ica_capture-0.1.0/README.md

@@ -0,0 +1,211 @@
+# ICA Capture SDK (Python)
+
+Emit your AI agent's steps to ICA in one line. ICA does the rest: it mints a
+signed, append-only receipt for every step, scores the run into continuous
+posture, and can halt an agent that crosses a control. You sign nothing and hold
+no key.
+
+A receipt of what ran is the floor. ICA also decides what is allowed to run: a
+gated call waits for ICA's decision before the tool body executes, a call held
+for people waits for their approval, and an agent that crosses a control can be
+halted. Each decision ICA seals carries a signed receipt that anyone can
+re-check later.
+
+## Install
+
+```bash
+pip install ica-capture            # core, zero dependencies
+pip install "ica-capture[callbacks]"   # adds the framework callback recorder
+```
+
+## Configure
+
+```python
+from ica import IcaClient
+
+ica = IcaClient(
+    token="YOUR_ICA_INGEST_TOKEN",   # X-ICA-Ingest-Token
+    agent_handle="your-agent",        # resolves to your registered identity
+)
+```
+
+Your ingest credential names your tenant, so `customer_id` is optional. If you
+pass it, it must be the same tenant: ICA refuses any other (403
+`ingest_tenant_mismatch`).
+
+Telemetry never breaks your agent. Emit failures are swallowed by default; pass
+`raise_on_error=True` while you are wiring things up.
+
+## Three drop-in surfaces
+
+### Callback recorder (one line)
+
+```python
+from ica.callbacks import IcaCallbackHandler
+
+agent.invoke(payload, config={"callbacks": [IcaCallbackHandler(ica)]})
+```
+
+Every tool call, ok or error, is recorded with timing, through the agent framework's own callback surface
+(install the `[callbacks]` extra).
+
+### Decorator
+
+```python
+from ica import ica_tool
+
+@ica_tool(ica, reversibility_tag="reversible")
+def search(query):
+    ...
+```
+
+### MCP or any callable
+
+```python
+from ica import wrap_mcp_tool
+
+guarded = wrap_mcp_tool(ica, raw_tool_call, name="filesystem.read")
+```
+
+### Manual
+
+```python
+ica.record_tool_call(
+    tool_name="web.search",
+    tool_input={"query": "..."},
+    tool_output={"hits": 3},
+    duration_ms=142,
+)
+```
+
+## What ICA does with it
+
+Each step posts to `POST /api/ingest/agent-step`. On arrival ICA:
+
+1. Mints an L7 receipt over the step, signed server-side. You never touch a key.
+2. Appends it to an append-only, tamper-evident audit trail.
+3. Feeds it to the assessment engine: decision control, containment,
+   reversibility, observability, continuous posture.
+4. Enforces. A step that bypasses a gate or runs an irreversible action ungated
+   is flagged, and a halted agent is quarantined at ingest.
+
+Verify any receipt without publishing your data. Public chains are optional, not
+required, and never the default.
+
+## Step fields
+
+| Field | Notes |
+|-------|-------|
+| `step_type` | `reasoning`, `tool_call`, `sub_agent_dispatch`, `final_answer`, `gate_request`, `gate_response` |
+| `tool_name` | the tool invoked |
+| `tool_input` / `tool_output` | JSON-safe; coerced if needed |
+| `reversibility_tag` | `reversible`, `partial`, `irreversible`, `unclassified` |
+| `gate_state` | `not_gated`, `pending`, `approved`, `denied`, `bypassed` |
+| `duration_ms`, `tokens_used` | optional metrics |
+
+## Tool guard and tool hooks
+
+For a graph whose held calls should wait for people, use `ica.approval_pause` (below): a held call pauses the
+graph instead of ending it, and the block is hard. The callback recorder above still records graph runs. Two
+more, neither of which adds a dependency. The agent framework is a setting, never a module name:
+
+| Use | `framework=` | Hard block with `gate=True` |
+|---|---|---|
+| `from ica.tool_guard import guard_tools`; `tools = guard_tools(ica, tools, framework=..., gate=True)` | `"openai_agents"` | yes: wraps each dataclass function tool's `on_invoke_tool` |
+| the same | `"crewai"` | yes: wraps each tool's `_run` |
+| the same | `"llamaindex"` | yes: wraps `FunctionTool` `_fn` and `_async_fn` |
+| `from ica.tool_hooks import IcaHooks`; `Agent(tools=..., hooks=[IcaHooks(ica, gate=True)])` | (frameworks that call tool hooks) | yes: a deny sets `cancel_tool` |
+
+An unknown `framework=` raises `ValueError`, so a typo never leaves tools unguarded. A tool of another shape is
+returned unchanged.
+
+## Stated confidence
+
+An agent can tell ICA how sure it is of each gated call, as a number from 0 to 1. When the agent's scope
+contract sets a confidence floor (`operating_envelope.confidence_floor`), ICA holds a call below the floor,
+or one that states nothing, for a person: `gate()` answers `pending` and the tool does not run. A high
+number never loosens anything; every other check still decides.
+
+- `ica.gate(action, tool_name=..., stated_confidence=0.82)` sends it on one call.
+- Every adapter and decorator takes `confidence=`: a number, or a function `(tool_name, payload) -> number`
+  that reads the model's own statement (for example a `confidence` field your tool schema asks the model to
+  fill). A function that raises states nothing, so with a floor set the call is held.
+
+```python
+tools = guard_tools(ica, tools, framework="crewai", gate=True, confidence=lambda name, payload: payload.get("kwargs", {}).get("confidence"))
+```
+
+## Approval pause: a held call pauses the graph
+
+Every other adapter treats a call ICA holds for a person (`pending`) as a deny: the run ends. In a graph runtime
+with `interrupt()` and a checkpointer the graph can wait instead.
+
+```python
+from langchain_core.tools import tool
+from langgraph.checkpoint.memory import MemorySaver
+from langgraph.prebuilt import ToolNode
+from ica.approval_pause import ica_approval_pause_tool, route_tool_calls
+
+@tool
+@ica_approval_pause_tool(ica, reversibility_tag="irreversible")
+def update_claim(claim_id: int, amount: int) -> str:
+    ...
+
+builder.add_node("tools", ToolNode([update_claim]))
+builder.add_conditional_edges("agent", route_tool_calls, ["tools", END])   # one task per tool call
+graph = builder.compile(checkpointer=MemorySaver())                       # pausing needs a checkpointer
+```
+
+- Approved: the tool runs and its step carries the single-use token. Denied: `GateDenied`, the tool never runs.
+- Held: ICA raises a two-person approval request bound to the exact arguments, and the graph pauses
+  (`interrupt()`); the payload carries `approval_request_id`. Two named people approve it in the ICA console.
+  Resume with `Command(resume=...)` (one value per pending interrupt when several pause at once). The resume
+  value is only a wake-up: the tool asks ICA, and runs only when ICA releases a token for that call. Still
+  pending, or ICA briefly unreachable: it pauses again. Denied, expired, arguments changed, or the agent halted,
+  retired or cert-blocked since the approval: `GateDenied`. Already released (a re-run after it ran): it does
+  not run again and returns a message saying so.
+- One tool call per task. A resumed graph task runs again from the top, and a plain `ToolNode` wired on the
+  messages list runs every call of a turn in one task, so the other calls of that turn would run again when one
+  pauses. Use `route_tool_calls` (above) or `create_react_agent` (its default version "v2" already sends each
+  call on its own). Tested with the graph runtime package at 1.2.14 (tests/test_approval_pause_real.py): with the routing, an approved call beside a held one runs once;
+  without it, twice.
+- Needs a per-customer ingest credential: only the credential that raised a request can collect it, and a
+  shared token raises none. A tenant that approves with one person gets no request either: this path releases
+  only on two named approvals. Outside a graph run nothing is requested and a hold ends the call, as before.
+- A request waits up to an hour for a person, an approval must be collected within an hour of being given, and a
+  credential can have at most 25 requests waiting. Arguments holding an integer past 2^53 are refused (JSON cannot
+  carry it exactly): send such ids as strings.
+- Each resume re-asks the gate (one more sealed `pending` decision). A `hold_key` derived from the thread and
+  task makes the re-ask find the same request. Pass `key_fn=` to name calls yourself.
+- Under it: `ica.gate(..., request_approval=True, args=..., hold_key=...)` and `ica.release(approval_request_id,
+  args)`, which any framework can use.
+
+## Signed proof in your agent's trace
+
+Every gate decision ICA seals comes back with its signed receipt. Give the client an `on_proof` function and that proof lands
+in your agent's own trace, beside the tool call it decided:
+
+```python
+ica = IcaClient(token="...", agent_handle="pay-bot", on_proof=add_to_current_run)
+```
+
+`add_to_current_run(proof)` is yours: add the dict to the current run's metadata in whatever tracing tool you use. The dict
+is flat strings: `ica_receipt_hash`, `ica_verify_url`, `ica_decision`, `ica_gate_id`, `ica_signing_key_id`, `ica_tool`.
+Anyone holding the hash re-checks the decision at the verify URL (public, no sign-in) or offline against ICA's published
+keys, without trusting your tracer or ALEETH. Every adapter above that gates (`gate=True`, the tool guard, the tool hooks,
+the approval pause) goes through `gate()`, so it carries the proof; the same dict is on the verdict as `verdict["proof"]`,
+and `proof_of(verdict)` builds it from any gate answer. A decision ICA could not seal gives no proof. A function that raises
+never changes the decision (it raises only with `raise_on_error=True`). A step recorded without a gate is signed just after
+ICA answers, so its receipt is not in that answer.
+
+## Outside eval results
+
+`from ica.evals import record_eval`, then `record_eval(ica, result, framework="ragas", run_name=..., thresholds={...})`.
+Reads Ragas, DeepEval, Giskard, TruLens, promptfoo and plain `{metric: score}` results, and files the
+summary (per-metric mean, min, max, count, pass and fail counts, failed thresholds, never the eval's
+prompts or answers) as one step on the agent's ICA record, where it is sealed like every other step.
+
+## License
+
+This SDK is licensed under the Apache License 2.0 (see LICENSE). Using ICA needs an ingest token: contact ALEETH
+(https://aleeth.com).

ica_capture-0.1.0/ica/__init__.py

@@ -0,0 +1,27 @@
+"""
+ICA capture SDK · emit agent steps; ICA governs and signs them.
+
+    from ica import IcaClient, ica_tool, wrap_mcp_tool
+    from ica.callbacks import IcaCallbackHandler          # optional: the [callbacks] extra
+    from ica.approval_pause import ica_approval_pause_tool   # optional: a held call pauses the agent's graph
+    from ica.tool_guard import guard_tools                # ICA in front of every tool; framework= is a setting
+    from ica.tool_hooks import IcaHooks                   # a hook provider for frameworks that call tool hooks
+"""
+
+from .client import IcaClient, IcaError, VALID_GATE_STATES, VALID_REVERSIBILITY, VALID_STEP_TYPES, proof_of
+from .decorator import GateDenied, ica_tool, wrap_mcp_tool
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "IcaClient",
+    "IcaError",
+    "proof_of",
+    "GateDenied",
+    "ica_tool",
+    "wrap_mcp_tool",
+    "VALID_STEP_TYPES",
+    "VALID_REVERSIBILITY",
+    "VALID_GATE_STATES",
+    "__version__",
+]