mitrity 0.2.0__tar.gz

mitrity-0.2.0/.gitignore

@@ -0,0 +1,36 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv*/
+venv/
+
+# Tooling
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+coverage.xml
+htmlcov/
+
+# Editors and OS
+.idea/
+.vscode/
+.DS_Store
+
+# Agent worktrees
+.claude/worktrees/
+
+# Files the review workflows write into a checkout when run locally
+/diff.txt
+/diff_truncated.txt
+/diff_nolock.txt
+/review.md
+/verdict.txt
+/comment.md
+/comment_truncated.md
+/untrusted_input.md
+/pr.json

mitrity-0.2.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 2026 MITRITY AB
+
+   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.

mitrity-0.2.0/PKG-INFO

@@ -0,0 +1,341 @@
+Metadata-Version: 2.5
+Name: mitrity
+Version: 0.2.0
+Summary: MITRITY governance adapter for Python agents: Claude Agent SDK, LangChain, OpenAI Agents SDK and CrewAI integrations for the MITRITY edge (admission API and gateway).
+Project-URL: Homepage, https://mitrity.com
+Project-URL: Source, https://github.com/mitrity-io/mitrity-python
+Project-URL: Contract, https://github.com/mitrity-io/iag-specs/blob/main/sentinel/adapters.md
+Author-email: MITRITY AB <hello@mitrity.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,claude-agent-sdk,crewai,governance,langchain,mcp,mitrity,openai-agents
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx<1,>=0.27
+Provides-Extra: claude-agent-sdk
+Requires-Dist: claude-agent-sdk>=0.2.157; extra == 'claude-agent-sdk'
+Provides-Extra: crewai
+Requires-Dist: crewai>=1.15; extra == 'crewai'
+Provides-Extra: dev
+Requires-Dist: anyio>=4.4; extra == 'dev'
+Requires-Dist: claude-agent-sdk>=0.2.157; extra == 'dev'
+Requires-Dist: crewai>=1.15; extra == 'dev'
+Requires-Dist: langchain-core>=1.0; extra == 'dev'
+Requires-Dist: mypy>=1.14; extra == 'dev'
+Requires-Dist: openai-agents>=0.20; extra == 'dev'
+Requires-Dist: pytest>=8.4; extra == 'dev'
+Requires-Dist: ruff>=0.8; extra == 'dev'
+Provides-Extra: langchain
+Requires-Dist: langchain-core>=1.0; extra == 'langchain'
+Provides-Extra: openai-agents
+Requires-Dist: openai-agents>=0.20; extra == 'openai-agents'
+Description-Content-Type: text/markdown
+
+# mitrity
+
+MITRITY governance adapter for Python agents: Claude Agent SDK, LangChain,
+OpenAI Agents SDK and CrewAI integrations for the MITRITY edge (admission API
+and gateway).
+
+The MITRITY gateway governs what an agent asks it to do over MCP. It cannot
+see what the agent's *framework* does on its own — the Agent SDK's `Bash`,
+`Write`, `Edit` and `WebFetch`, a LangChain `ShellTool`. This package closes
+that gap: every such call is admitted by the co-located edge **before it
+runs**, with the same policy rules, command analysis, DLP and holds an MCP call
+gets, and the same audit trail (`surface=agent_hook`). If the edge cannot be
+reached, the call is denied — there is no fail-open mode.
+
+Contract: [iag-specs/sentinel/adapters.md](https://github.com/mitrity-io/iag-specs/blob/main/sentinel/adapters.md)
+(wire protocol: [sentinel/admission-api.md](https://github.com/mitrity-io/iag-specs/blob/main/sentinel/admission-api.md)).
+
+## Install
+
+Until the first PyPI release, install from git at a pinned ref (a release tag
+once one exists, a commit SHA until then):
+
+```bash
+pip install "mitrity[claude-agent-sdk] @ git+https://github.com/mitrity-io/mitrity-python.git@<ref>"
+pip install "mitrity[langchain] @ git+https://github.com/mitrity-io/mitrity-python.git@<ref>"
+pip install "mitrity[openai-agents] @ git+https://github.com/mitrity-io/mitrity-python.git@<ref>"
+pip install "mitrity[crewai] @ git+https://github.com/mitrity-io/mitrity-python.git@<ref>"
+```
+
+Python ≥ 3.10. The only runtime dependency is `httpx`; the framework extras
+pull in `claude-agent-sdk`, `langchain-core`, `openai-agents` and `crewai`
+respectively.
+
+## Prerequisite: a co-located edge
+
+The adapter talks to a `mitrity-gateway` (or `mitrity-mcp-sidecar`) running
+next to the agent with an `admission` block:
+
+```yaml
+admission:
+  enabled: true
+  listen_addr: "unix:/run/mitrity/admission.sock"
+  token_file: "/run/mitrity/admission.token"
+```
+
+The adapter finds it through the same environment variables `mitrity-hook`
+uses, with the same defaults:
+
+| Variable | Default | Meaning |
+| --- | --- | --- |
+| `MITRITY_ADMISSION_ADDR` | `unix:/run/mitrity/admission.sock` (`127.0.0.1:8777` on Windows) | The edge's admission listener. Must be a Unix socket or loopback; anything else is refused. |
+| `MITRITY_ADMISSION_TOKEN_FILE` | `/run/mitrity/admission.token` | The per-process token the edge writes at startup. |
+| `MITRITY_HOOK_TIMEOUT` | `500ms` (max `30s`) | Deadline for one decision. |
+| `MITRITY_HOOK_HOLD_TIMEOUT` | `540s` (max `570s`) | Longest to wait on a human approval; `0` disables waiting. |
+| `MITRITY_HOOK_FAIL_MODE` | — | Ignored. Adapters have no fail-open mode. |
+
+## Claude Agent SDK
+
+```python
+from claude_agent_sdk import query
+from mitrity.claude_agent_sdk import governed_options
+
+options = governed_options(
+    gateway={
+        "type": "stdio",
+        "command": "mitrity-gateway",
+        "args": ["--config", "/etc/mitrity/gateway.yaml"],
+    },
+    allowed_tools=["Bash", "Read", "Write", "mcp__mitrity"],
+    system_prompt="You are a careful engineering agent.",
+)
+
+async for message in query(prompt="Clean up the build directory", options=options):
+    print(message)
+```
+
+What `governed_options()` does:
+
+- Installs a `PreToolUse` hook over the execution-capable built-ins (`Bash`,
+  `Write`, `Edit`, `MultiEdit`, `NotebookEdit`, `WebFetch`, `WebSearch`) that
+  asks the edge before each call. An allow is silent, so your own
+  `allowed_tools` / `can_use_tool` flow still applies on top. A deny reaches
+  the model as `permissionDecision: "deny"` with the policy reason. A hold
+  waits for a human (up to `MITRITY_HOOK_HOLD_TIMEOUT`) and is a deny if nobody
+  approves.
+- Pins `mcp_servers` to the gateway entry (plus anything you add, which is
+  reported as ungoverned), sets `strict_mcp_config=True` and
+  `setting_sources=[]` unless you override them.
+- Attests the runtime's posture (`POST /v1/attest`) on the first prompt of
+  each session: which tools are hooked, which are not, other MCP servers,
+  permission mode, sandbox settings. The Python SDK has no `SessionStart`
+  callback hook, so the first `UserPromptSubmit` is the trigger.
+- Keeps every other option you pass. Your own hooks run after MITRITY's; a
+  deny from any hook wins.
+
+For statistics or the attestation object, build the `Governor` yourself:
+
+```python
+from mitrity.claude_agent_sdk import Governor
+
+governor = Governor(gateway=gateway_config)
+options = governor.options(allowed_tools=["Bash"])
+...
+print(governor.stats)  # admitted / allowed / denied / held / unreachable / routed
+print(governor.attestation())  # what the control plane was told
+```
+
+### Routed Bash (governed shell)
+
+When the agent's policy sets `builtin_exec_routing: governed_shell`, an
+allowed `Bash` comes back with `updated_input` rewriting the command to
+`mitrity-hook exec <ticket>`. The adapter emits it as `updatedInput` with an
+explicit allow, and the framework runs the relay instead of the model's
+command; the gateway executes the judged bytes in its own sandbox. This needs
+the `mitrity-hook` binary on `PATH` and a gateway with `exec.enabled: true`.
+
+### Two approval records per hold
+
+The adapter asks twice for a held action: once without waiting (so an
+unreachable edge is noticed in milliseconds), then again with the hold budget.
+The edge creates an approval for each; resolve whichever is pending. The
+stale one times out on its own. This matches `mitrity-hook`.
+
+## LangChain
+
+```python
+from langchain_community.tools import ShellTool
+from mitrity.langchain import govern_tools
+
+tools = govern_tools([ShellTool(), my_write_tool], session_id=thread_id)
+```
+
+`govern(tool)` returns a `BaseTool` with the same name, description and
+schema. Its `_run` / `_arun` admit the call first; a deny raises
+`ToolException` with the edge's reason (set `handle_tool_error=True` on the
+tool if you want the reason fed back to the model as an error result rather
+than raised), and an `updated_input` from the edge replaces the arguments
+before the wrapped tool runs.
+
+Two limits:
+
+- **Coverage is what you hand it.** A tool that did not go through `govern`
+  is invisible to the adapter and to the attestation. `govern_tools` is the
+  boundary.
+- **Argument names stay yours.** The edge parses commands from the keys
+  `command`, `cmd`, `script`, `args` and `argv`. LangChain's `ShellTool`
+  calls its argument `commands`, which today is DLP- and content-scanned but
+  not parsed as a command tree. The adapter does not rename it; that key
+  joins the edge's command family on the edge side.
+
+The session id is, in order: the `session_id` you pass, the
+`configurable.thread_id` of the run config, or one id per process.
+
+## OpenAI Agents SDK
+
+```python
+from agents import Agent, Runner, ShellTool, function_tool
+from mitrity.openai_agents import govern
+
+
+@function_tool
+def run_command(command: str) -> str:
+    """Run a shell command on the build host and return its output."""
+    ...
+
+
+agent = govern(Agent(name="ops", tools=[run_command, ShellTool(executor=my_executor)]))
+result = await Runner.run(agent, "clean up the build directory")
+```
+
+`govern(agent)` returns a clone of the agent whose tools ask the edge before
+they run; `govern_tools(tools)` does the same for a list. Each tool type is
+blocked the way the SDK itself blocks that type:
+
+- A **function tool** gets a *tool input guardrail*: a deny is
+  `reject_content` with the policy reason, which the SDK hands to the model
+  as the tool's output without running the tool. An allow is silent. An
+  `updated_input` from the edge is merged into the JSON arguments the
+  function receives.
+- **`ShellTool`** and **`ApplyPatchTool`** go through the SDK's approval
+  flow: the adapter's `needs_approval` asks the edge, and on a deny its
+  `on_approval` rejects the call with the reason — as it rejects an approval
+  it cannot tie to a decision it made. Your own `needs_approval` and
+  `on_approval` still apply when MITRITY allows. The execution channel is
+  gated as well: the wrapped shell executor and the wrapped `apply_patch`
+  editor re-check the decision `needs_approval` made, and admit a call the
+  SDK runs without asking (an approved call on a resumed run); a deny there
+  reaches the model as the tool's failed output. The shell executor runs the
+  edge's rewritten `commands` when it sends them; an `apply_patch` rewrite
+  is a deny (the editor receives the operation alone, with nothing to apply
+  a rewrite to). A `ShellTool` whose `environment` is a hosted container
+  runs in OpenAI's cloud and passes through like the hosted tools below.
+- **`LocalShellTool`** (deprecated upstream) has neither a guardrail nor an
+  approval, so a deny is returned as the executor's output with nothing run.
+- **Hosted tools** (web search, file search, code interpreter, image
+  generation, hosted MCP) run in OpenAI's cloud and `ComputerTool` drives a
+  computer the SDK does not judge: they pass through untouched and are
+  reported as ungoverned in the attestation.
+
+Judged bytes are the executed bytes. A decision is kept for the tool, the
+SDK's `call_id` and a digest of the input it was made for; the invoker,
+executor or editor reuses it only for that exact input, and an execution
+whose input differs from what the edge judged raises `MitrityDenied` rather
+than running under that decision.
+
+MCP servers on the agent are not touched. Pass the MITRITY gateway server as
+`gateway=` so it is not reported as ungoverned; every other server is. The
+session id is, in order: the `session_id` you pass, `RunConfig.group_id`, or
+one id per process. Handoff targets given as `Agent` objects are governed
+too, once each — a specialist handing back to the triage agent, or two paths
+to the same agent, resolve to one governed clone; a `Handoff` object built
+with `handoff()` is left as is, so govern its agent before building it. A
+tool type the adapter does not know passes through with a warning and is
+reported as ungoverned.
+
+## CrewAI
+
+```python
+from crewai import Agent
+from mitrity.crewai import govern_tools
+
+agent = Agent(role="ops", goal="...", backstory="...", tools=govern_tools([terminal, writer]))
+```
+
+`govern(tool)` returns a `BaseTool` with the same name, description and
+schema whose `_run` / `_arun` admit the call first. A deny is returned as a
+`ToolFailure` carrying the policy reason — CrewAI's declared channel for a
+tool that did not do what it was asked: the agent sees the reason, the
+failure is recorded on the task output, and the agent's `tool_failure_policy`
+decides whether to continue or abort. An `updated_input` from the edge
+replaces the arguments before the wrapped tool runs; a rewrite of several
+positional arguments must cover every one of them or the call is blocked.
+
+A governed tool never caches: CrewAI's tool cache would replay an earlier
+result for the same arguments without the edge judging the call again, so
+the inner tool's `cache_function` is not copied and the governed one always
+answers no. Govern a tool before its first run — the crew reads its cache by
+tool name before the tool is reached, so a result an ungoverned run of the
+same tool cached earlier would still be served.
+
+Coverage is what you hand it. Tools CrewAI adds to an agent on its own — the
+delegation tools, the code interpreter behind `allow_code_execution=True`,
+MCP tools from `mcps` — never pass through `govern` and are invisible to the
+adapter; on Linux hosts the MITRITY observer reports their executions after
+the fact.
+
+## The wire client
+
+Both integrations sit on `mitrity.admission.Client`, which you can use for
+any framework:
+
+```python
+from mitrity.admission import AdmitRequest, Client
+
+client = Client()  # discovers the edge from the environment
+verdict = client.decide(
+    AdmitRequest(surface="custom", tool_name="Bash", tool_input={"command": "rm -rf build"})
+)
+if not verdict.allowed:
+    raise RuntimeError(verdict.reason)
+```
+
+`decide()` never raises: it returns a `Verdict` whose `reason` is safe to
+show the model and whose `error` is set when the deny is the adapter's own
+(the edge could not be reached) rather than a policy decision. `admit()` is
+the single round trip and raises an `AdmissionError` subclass on any failure.
+Async variants: `decide_async`, `admit_async`, `attest_async`.
+
+## What is not governed
+
+- Tools outside the hook matcher, or LangChain / CrewAI tools not passed to
+  `govern`. The attestation names them; the MITRITY dashboard shows the gap.
+- Hosted tools of the OpenAI Agents SDK (they run in the vendor's cloud) and
+  its `ComputerTool`; reported as ungoverned in the attestation.
+- The agent's own code: `subprocess.run` in your application never passes a
+  tool boundary. On Linux hosts the MITRITY observer reports it after the
+  fact.
+- Removing the adapter. It is your code; the control plane detects the
+  missing attestation and the silent admission counters, it cannot prevent
+  the edit.
+
+## Development
+
+```bash
+python -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"
+ruff check . && ruff format --check . && mypy --strict && pytest
+```
+
+Tests run against an in-process fake edge over a Unix socket; no MITRITY
+account and no network are needed. The conformance tests are numbered after
+the contract (`C1`–`C28`).
+
+## Security
+
+See [SECURITY.md](SECURITY.md). Report vulnerabilities to soc@mitrity.com.
+
+## License
+
+Apache-2.0. Copyright 2026 MITRITY AB.