cirvix 0.1.0__tar.gz

cirvix-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+node_modules/
+*.tgz
+.cirvix/
+__pycache__/
+*.pyc
+dist/
+build/
+*.egg-info/
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+.DS_Store

cirvix-0.1.0/LICENSE

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

cirvix-0.1.0/NOTICE

@@ -0,0 +1,42 @@
+Cirvix AgentControl — enforcement engine
+Copyright 2026 Umang Kumar, trading as Cirvix
+
+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.
+
+---
+
+WHAT THIS LICENCE COVERS
+
+This package is the enforcement engine: the policy evaluator, the risk
+classifier, the secret detector and handle substitution, the local control
+socket, the MCP gateway, the audit chain, the scanner, and the `cirvix` CLI.
+
+It is licensed under Apache 2.0 deliberately. A security control that cannot be
+read is a security control you are asked to take on faith, and this is the part
+that decides whether a tool call runs. Read it, fork it, audit it, run it in
+production without paying anything, and do not ask us for permission.
+
+WHAT IT DOES NOT COVER
+
+The Cirvix control plane — multi-tenant policy distribution, the team vault,
+SSO and SCIM, approvals workflow, hosted audit retention and export, compliance
+evidence reporting, fleet telemetry and billing — is a separate package under a
+separate, proprietary licence. See packages/control-plane/LICENSE.
+
+THIRD-PARTY CODE
+
+There is none. This package has zero runtime dependencies, deliberately and
+permanently — a security tool that drags in a transitive dependency tree is
+asking to become the supply-chain incident it exists to prevent.
+
+The self-hosted fonts shipped with the Cirvix website (Geist and Geist Mono) are
+licensed SIL OFL-1.1 and are not part of this package.

cirvix-0.1.0/PKG-INFO

@@ -0,0 +1,145 @@
+Metadata-Version: 2.5
+Name: cirvix
+Version: 0.1.0
+Summary: Runtime governance for AI agents — evaluate every tool call against policy before it executes.
+Project-URL: Homepage, https://www.cirvix.com
+Project-URL: Documentation, https://www.cirvix.com/sdks.html
+Author: Cirvix
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agents,ai,governance,llm,mcp,policy,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+
+# cirvix
+
+Runtime governance for Python AI agents. Every tool call is evaluated against
+policy before it executes.
+
+**Zero dependencies.** Standard library only, permanently — the same reason the
+Node package has none.
+
+```bash
+pip install cirvix
+```
+
+**Full documentation:** [`docs/`](../../docs/) — [Python SDK](../../docs/sdk-python.md), [policy reference](../../docs/policy.md), [quickstart](../../docs/quickstart.md).
+
+## Governing an agent
+
+```python
+from cirvix import guard, CirvixDenied, CirvixHeld
+
+tools = guard.wrap(
+    my_tools,
+    agent="pr-triage",
+    environment=os.environ.get("CIRVIX_ENV", "local"),
+    rules=rules,
+)
+
+try:
+    crew.kickoff()
+except CirvixHeld as held:
+    print(held.approvers)     # ["platform-oncall"] — this call is waiting
+except CirvixDenied as err:
+    print(err.policy)         # "deny-dotenv-read"
+    print(err.remediation)    # 'secrets.get("STRIPE_KEY")'
+    print(err.decision_id)    # pass to `cirvix why`
+```
+
+`wrap` accepts the shapes Python tool collections actually come in and returns
+the same shape:
+
+| It accepts | Framework |
+|---|---|
+| A mapping of `name -> callable` | hand-rolled loops, AutoGen function maps |
+| A sequence of objects carrying `func` | LangChain |
+| A sequence of objects carrying `_run` | CrewAI |
+| A single callable | anything |
+
+Async tools stay async. Tool objects keep their descriptions and schemas, and
+the list you passed in is left alone — a framework holding the originals does
+not find them governed by surprise.
+
+**`CirvixDenied` vs `CirvixHeld`.** A denial means re-plan. A hold means this
+exact call may still happen once a person says yes. They are separate types
+because collapsing them teaches an agent to treat both as failure.
+
+## Why this is a real evaluator and not an HTTP client
+
+The easy version of this package asks a control plane over the network for
+every decision. That would have been a fraction of the work and it would have
+been wrong twice over: it puts a round trip in the enforcement path, and it
+breaks the offline-first property the whole product rests on — a control plane
+that stops enforcing when the network blips is worse than none, because the
+failure is invisible.
+
+So this is a native port. Which raises the real risk: **two engines that can
+silently disagree are worse than one engine and an honest gap.** An agent
+denied by the Node gateway and permitted here is a bypass nobody would find
+until it mattered.
+
+What makes it safe is `packages/conformance/policy-conformance.json`. Both
+engines load that file and must produce identical verdicts, rules, canonical
+resources, and rule traces across 44 cases — forbid short-circuiting, hold
+outranking permit, default deny, glob semantics, path traversal, URL
+normalization, every comparator, and the fail-closed behaviour for unknown
+ones. Neither language gets a private copy, and changing behaviour means
+changing the fixture first, in a commit a reviewer can see.
+
+It has already earned its keep: writing it surfaced a bug where the Node engine
+canonicalized `/etc/passwd` to `C:/etc/passwd` on Windows, so a rule written
+`resources: ["/etc/**"]` silently did not match on the machine it was most
+likely written to protect.
+
+```bash
+python -m unittest discover -s tests
+```
+
+## Testing a policy like code
+
+```python
+from cirvix.testing import evaluate, expect_no_loosening
+
+def test_production_writes_are_held():
+    decision = evaluate(
+        policy_dir="./policies",
+        agent="deploy-bot",
+        action="k8s.apply",
+        resource="production/checkout",
+        context={"environment": "production"},
+    )
+    assert decision.verdict == "hold"
+    assert "platform-oncall" in decision.approvers
+```
+
+`expect_no_loosening(before=…, after=…, calls=…)` reports any call a policy
+change would newly permit. Tightening passes — a security policy is allowed to
+move that way without surprising a reviewer.
+
+## What `wrap` does not do
+
+The MCP gateway governs everything an agent does, **including tools added after
+you deployed it**, because it sits on the wire. `wrap` governs a list. You keep
+the same engine, rules, decision records, and audit chain; you give up coverage
+of tools you did not enumerate.
+
+If your agent speaks MCP — Claude Code, Cursor, or anything else — use the
+gateway instead:
+
+```bash
+cirvix gateway --servers ~/.cursor/mcp.json
+```
+
+## Status
+
+Pre-release. The policy engine, `guard.wrap`, and the testing helpers work
+today. Not yet in this package: secret-handle brokering and telemetry shipping,
+both of which the Node SDK has — until then, point Python agents at the gateway
+if you need those.

cirvix-0.1.0/README.md

@@ -0,0 +1,126 @@
+# cirvix
+
+Runtime governance for Python AI agents. Every tool call is evaluated against
+policy before it executes.
+
+**Zero dependencies.** Standard library only, permanently — the same reason the
+Node package has none.
+
+```bash
+pip install cirvix
+```
+
+**Full documentation:** [`docs/`](../../docs/) — [Python SDK](../../docs/sdk-python.md), [policy reference](../../docs/policy.md), [quickstart](../../docs/quickstart.md).
+
+## Governing an agent
+
+```python
+from cirvix import guard, CirvixDenied, CirvixHeld
+
+tools = guard.wrap(
+    my_tools,
+    agent="pr-triage",
+    environment=os.environ.get("CIRVIX_ENV", "local"),
+    rules=rules,
+)
+
+try:
+    crew.kickoff()
+except CirvixHeld as held:
+    print(held.approvers)     # ["platform-oncall"] — this call is waiting
+except CirvixDenied as err:
+    print(err.policy)         # "deny-dotenv-read"
+    print(err.remediation)    # 'secrets.get("STRIPE_KEY")'
+    print(err.decision_id)    # pass to `cirvix why`
+```
+
+`wrap` accepts the shapes Python tool collections actually come in and returns
+the same shape:
+
+| It accepts | Framework |
+|---|---|
+| A mapping of `name -> callable` | hand-rolled loops, AutoGen function maps |
+| A sequence of objects carrying `func` | LangChain |
+| A sequence of objects carrying `_run` | CrewAI |
+| A single callable | anything |
+
+Async tools stay async. Tool objects keep their descriptions and schemas, and
+the list you passed in is left alone — a framework holding the originals does
+not find them governed by surprise.
+
+**`CirvixDenied` vs `CirvixHeld`.** A denial means re-plan. A hold means this
+exact call may still happen once a person says yes. They are separate types
+because collapsing them teaches an agent to treat both as failure.
+
+## Why this is a real evaluator and not an HTTP client
+
+The easy version of this package asks a control plane over the network for
+every decision. That would have been a fraction of the work and it would have
+been wrong twice over: it puts a round trip in the enforcement path, and it
+breaks the offline-first property the whole product rests on — a control plane
+that stops enforcing when the network blips is worse than none, because the
+failure is invisible.
+
+So this is a native port. Which raises the real risk: **two engines that can
+silently disagree are worse than one engine and an honest gap.** An agent
+denied by the Node gateway and permitted here is a bypass nobody would find
+until it mattered.
+
+What makes it safe is `packages/conformance/policy-conformance.json`. Both
+engines load that file and must produce identical verdicts, rules, canonical
+resources, and rule traces across 44 cases — forbid short-circuiting, hold
+outranking permit, default deny, glob semantics, path traversal, URL
+normalization, every comparator, and the fail-closed behaviour for unknown
+ones. Neither language gets a private copy, and changing behaviour means
+changing the fixture first, in a commit a reviewer can see.
+
+It has already earned its keep: writing it surfaced a bug where the Node engine
+canonicalized `/etc/passwd` to `C:/etc/passwd` on Windows, so a rule written
+`resources: ["/etc/**"]` silently did not match on the machine it was most
+likely written to protect.
+
+```bash
+python -m unittest discover -s tests
+```
+
+## Testing a policy like code
+
+```python
+from cirvix.testing import evaluate, expect_no_loosening
+
+def test_production_writes_are_held():
+    decision = evaluate(
+        policy_dir="./policies",
+        agent="deploy-bot",
+        action="k8s.apply",
+        resource="production/checkout",
+        context={"environment": "production"},
+    )
+    assert decision.verdict == "hold"
+    assert "platform-oncall" in decision.approvers
+```
+
+`expect_no_loosening(before=…, after=…, calls=…)` reports any call a policy
+change would newly permit. Tightening passes — a security policy is allowed to
+move that way without surprising a reviewer.
+
+## What `wrap` does not do
+
+The MCP gateway governs everything an agent does, **including tools added after
+you deployed it**, because it sits on the wire. `wrap` governs a list. You keep
+the same engine, rules, decision records, and audit chain; you give up coverage
+of tools you did not enumerate.
+
+If your agent speaks MCP — Claude Code, Cursor, or anything else — use the
+gateway instead:
+
+```bash
+cirvix gateway --servers ~/.cursor/mcp.json
+```
+
+## Status
+
+Pre-release. The policy engine, `guard.wrap`, and the testing helpers work
+today. Not yet in this package: secret-handle brokering and telemetry shipping,
+both of which the Node SDK has — until then, point Python agents at the gateway
+if you need those.

cirvix-0.1.0/cirvix/__init__.py

@@ -0,0 +1,85 @@
+"""Cirvix AgentControl — runtime governance for Python AI agents.
+
+Zero dependencies, standard library only. A security tool that drags in a
+transitive dependency tree is asking to become the supply-chain incident it
+exists to prevent.
+
+    from cirvix import guard, CirvixDenied
+
+    tools = guard.wrap(my_tools, agent="pr-triage", rules=rules)
+
+    try:
+        crew.kickoff()
+    except CirvixDenied as err:
+        print(err.policy)       # "deny-dotenv-read"
+        print(err.remediation)  # 'secrets.get("STRIPE_KEY")'
+        print(err.decision_id)  # pass to `cirvix why`
+
+Enforcement is identical to the Node SDK and the MCP gateway, and that is not a
+claim resting on care: all three run the shared conformance suite in
+``packages/conformance/policy-conformance.json``.
+"""
+
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError, version as package_version
+
+from .guard import (
+    CirvixDenied,
+    CirvixHeld,
+    Guard,
+    action_for_tool,
+    destination_for,
+    resource_for_call,
+    wrap,
+)
+from .policy import (
+    EFFECT,
+    STARTER_RULES,
+    VERDICT,
+    Decision,
+    canonicalize_resource,
+    evaluate,
+    match_glob,
+    parse_rules,
+)
+
+try:
+    __version__ = package_version("cirvix")
+except PackageNotFoundError:
+    # Source checkouts are not installed distributions. The package metadata
+    # and VERSION file are checked together by tools/check-version.mjs.
+    __version__ = "0.1.0"
+
+__all__ = [
+    "CirvixDenied",
+    "CirvixHeld",
+    "Decision",
+    "EFFECT",
+    "Guard",
+    "STARTER_RULES",
+    "VERDICT",
+    "action_for_tool",
+    "canonicalize_resource",
+    "destination_for",
+    "evaluate",
+    "guard",
+    "match_glob",
+    "parse_rules",
+    "resource_for_call",
+    "wrap",
+]
+
+
+class _GuardNamespace:
+    """The documented entry point: ``guard.wrap(tools, ...)``.
+
+    A namespace rather than a module so ``from cirvix import guard`` reads the
+    same way as the Node SDK's ``import { guard }``.
+    """
+
+    wrap = staticmethod(wrap)
+    Guard = Guard
+
+
+guard = _GuardNamespace()