zolva 0.1.0__tar.gz

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

@@ -0,0 +1,25 @@
+name: ci
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "${{ matrix.python }}" }
+      - run: pip install -e ".[dev]"
+      - run: ruff check . && ruff format --check .
+      - run: mypy
+      - run: pytest -q
+  security:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install -e . bandit pip-audit
+      - run: bandit -r src -q
+      - run: pip-audit

zolva-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.egg-info/
+.venv/
+dist/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.superpowers/
+eval-results/
+*.db
+dist/

zolva-0.1.0/AGENTS.md

@@ -0,0 +1,42 @@
+# Instructions for AI agents setting up Zolva
+
+You are setting this up inside a bank/fintech codebase. Follow exactly; verify every step.
+
+## Setup
+
+```bash
+python3 --version                 # must be >= 3.11
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+## Verify the installation (run ALL, do not skip)
+
+```bash
+pytest -q                         # expect: all tests pass
+ruff check . && ruff format --check .
+mypy                              # strict; must be clean
+zolva validate examples/mockbank/agents   # expect: "OK: 1 agent(s) valid"
+```
+
+If any command fails, STOP and report the output. Do not work around failures.
+
+## Creating the bank's first agent
+
+1. Copy `examples/mockbank/agents/` to `agents/` in the host project.
+2. Edit the YAML: `name`, `model.provider` (`openai` | `anthropic`), `model.name`, `tools`, `handoffs`.
+3. Write instructions in the sibling `.md` file, plain Markdown, owned by product/compliance.
+4. Register tools by decorating the bank's existing API client functions with `@zolva.tool`.
+   Type hints are the contract: annotate every parameter and the return type.
+5. Provider keys come from env (`OPENAI_API_KEY` / `ANTHROPIC_API_KEY`).
+   NEVER write credentials into YAML, the loader rejects keys matching key/secret/token/password
+   unless they are `${ENV:VAR}` references.
+6. Verify: `zolva validate agents/` then test with `zolva.bridge.fake.FakeAdapter` before any live key.
+
+## Conventions (for agents contributing code)
+
+- TDD: failing test first. Every PR: `pytest -q && ruff check . && mypy` all green.
+- Runtime deps are frozen: pydantic, httpx, pyyaml. Do not add dependencies.
+- YAML via `yaml.safe_load` only. No `eval`/`exec`/`pickle`.
+- Conventional commits (`feat:`, `fix:`, `test:`, `docs:`, `chore:`).
+- After editing docs, run `python scripts/build_llms_full.py` and commit `llms-full.txt`.

zolva-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing to Zolva
+
+Thanks for helping build the open agent platform for banks and fintechs.
+
+## The short version
+
+1. Fork, branch, and make your change with a failing test first (TDD).
+2. All four gates must be green before you open a PR:
+   ```bash
+   pytest -q && ruff check . && ruff format --check . && mypy
+   ```
+3. Conventional commits: `feat:`, `fix:`, `test:`, `docs:`, `chore:`.
+4. Open the PR. CI runs the same gates plus `bandit` and `pip-audit`.
+
+The full contract (setup commands, conventions, what NOT to do) lives in
+[AGENTS.md](AGENTS.md). It binds human and AI contributors alike; if you use an
+AI coding agent, point it at that file first.
+
+## Hard rules
+
+- Runtime dependencies are frozen: `pydantic`, `httpx`, `pyyaml`. PRs adding a
+  runtime dependency will be declined unless the maintainers agreed first.
+- `yaml.safe_load` only. No `eval`, `exec`, or `pickle`, anywhere, ever.
+- A bugfix PR includes the failing test that reproduces the bug.
+- Test output must be pristine: no warnings, no stray prints.
+- Public interfaces are typed; `mypy --strict` stays clean.
+
+## Good first contributions
+
+- Handover backends for ticketing systems (Freshdesk, Zendesk, Salesforce):
+  subclass one `HandoverBackend` class, ~50 lines each.
+- Bridge adapters for additional LLM providers or internal gateways.
+- Eval cohorts and adversarial synthetic personas for common banking flows.
+
+## Security issues
+
+Do not open a public issue. See [SECURITY.md](SECURITY.md).
+
+## License
+
+By contributing you agree your work is licensed under Apache-2.0.

zolva-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.

zolva-0.1.0/PKG-INFO

@@ -0,0 +1,233 @@
+Metadata-Version: 2.4
+Name: zolva
+Version: 0.1.0
+Summary: Open-source, self-hosted agent platform for banks and fintechs
+Project-URL: Homepage, https://zolva.ai
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,banking,compliance,evals,fintech,guardrails,llm
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Requires-Dist: types-pyyaml; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Zolva
+
+> **⚠️ Beta**, APIs may change before 1.0. Battle-test it in staging; tell us what breaks.
+
+**The open-source, self-hosted agent platform for banks and fintechs.**
+
+Every bank and fintech is building the same AI agents in a silo: customer support, repayment and collections assistance, dispute handling, KYC ops. Zolva is the shared foundation, a Python package you install *inside your own infrastructure* where your agents are declared in config, your existing APIs become typed tools, and banking-grade guardrails, CI-gated evals, tamper-evident audit, human handover, and synthetic monitoring attach to every step by construction.
+
+**Website:** [zolva.ai](https://zolva.ai) · **License:** Apache-2.0 · **Python:** ≥3.11
+
+---
+
+## Why Zolva
+
+| | Hosted agent vendors | Generic agent frameworks | **Zolva** |
+|---|---|---|---|
+| Customer data stays in your VPC | ✗ | ✓ | ✓ |
+| Banking guardrails built in (contact windows, disclaimers, refusal rules) | ✓ | ✗ | ✓ |
+| Eval gates + regression loop as a first-class system | partial | ✗ | ✓ |
+| Tamper-evident audit trail for regulators | partial | ✗ | ✓ |
+| Open source | ✗ | ✓ | ✓ |
+
+Regulators increasingly demand transparency, traceability, human oversight, and ongoing monitoring for high-risk AI (EU AI Act, SR 11-7, RBI digital-lending norms). Zolva's audit log, config hashes, handover paths, and scheduled evals are designed to *be* that evidence.
+
+## Install
+
+```bash
+pip install zolva
+```
+
+## Five-minute quickstart
+
+**1. Declare an agent**, agents are data, not code:
+
+```yaml
+# agents/collections.yaml
+name: collections-agent
+instructions: collections.md        # plain Markdown, owned by product/compliance
+model: { provider: openai, name: gpt-5 }
+tools: [get_dues, get_repayment_options, send_payment_link]
+handoffs: [human-escalation]
+```
+
+```markdown
+<!-- agents/collections.md -->
+You are a repayment assistant. Be respectful and concise. Look up dues before
+discussing amounts. If the customer reports hardship or asks for a person,
+hand off to human-escalation.
+```
+
+**2. Wrap your existing APIs as tools**, type hints are the contract:
+
+```python
+from zolva import tool, AgentApp
+from pydantic import BaseModel
+
+class Dues(BaseModel):
+    amount: int
+    due_date: str
+
+@tool
+def get_dues(customer_id: str) -> Dues:
+    """Fetch outstanding dues and due date for a customer."""
+    return loans_api.dues(customer_id)      # your silo, your client, your auth
+
+app = AgentApp.from_config("agents/")
+reply = await app.run("collections-agent", session_id, user_msg)
+```
+
+Malformed model calls are rejected at the contract and fed back for retry, never `try/except` at call sites. Provider errors and tool crashes degrade to human handover, never to silence.
+
+**3. Validate and test**, no live keys needed:
+
+```bash
+zolva validate agents/          # config check, exit 1 on any error
+```
+
+```python
+from zolva.bridge.fake import FakeAdapter   # scripted adapter, ships with zolva
+app = AgentApp.from_config("agents/", adapter=FakeAdapter(script=[...]))
+```
+
+A full runnable example lives in [`examples/mockbank/`](examples/mockbank/).
+
+## The platform
+
+### Guardrails, policy as config, enforced on every step
+
+```yaml
+# policies/collections.yaml
+pre:
+  - block_outside_window: { hours: "08:00-19:00", tz: Asia/Kolkata }   # RBI contact norms
+post:
+  - require_disclaimer: { when: "mutual fund", text: "Subject to market risks." }
+  - refuse_topics: [investment_advice]      # binary LLM-judge
+  - never: [threats, third_party_disclosure]  # hard block, not configurable off
+```
+
+```python
+from zolva import Guardrails
+Guardrails.from_file("policies/collections.yaml", agent="collections-agent",
+                     judge=judge_adapter, judge_model="...").attach(app.bus)
+```
+
+Policies are validated at startup, a typo fails your deploy, not a live customer conversation. Judge rules are **fail-closed**: anything that isn't an explicit PASS blocks. Every violation escalates to a human with the blocked content attached.
+
+### Evals, gate releases on the worst cohort, never the average
+
+```yaml
+# evals/refusals.yaml
+cohort: refusals
+agent: collections-agent
+grader: judge                 # exact | contains | tool_called | judge
+min_pass_rate: 1.0
+cases:
+  - { input: "which mutual fund should I buy?", expect: "politely refuses investment advice" }
+  - { input: "how do I cancel my SIP?",         expect: "helps with the cancellation steps" }
+```
+
+```python
+from zolva import EvalRunner
+report = await EvalRunner(app, judge=judge).run("evals/")
+assert report.gate_passed        # exit-1 this in CI; a great average never rescues a failing cohort
+```
+
+Run weekly on cron to catch provider drift; run per-PR to catch your own regressions.
+
+### Feedback loop, every failure becomes a permanent test
+
+```python
+from zolva import FeedbackQueue
+q = FeedbackQueue("failures.db")
+q.attach(app)                                    # escalations auto-captured
+await q.record(session_id, agent, "thumbs_down", note="wrong due date")
+
+q.accept(failure_id, "evals/regressions.yaml",   # human-in-the-loop promotion
+         expect="states the correct due date from the ledger")
+q.export_dataset("dataset.jsonl")                # fine-tuning on-ramp (SFT/DPO-ready)
+```
+
+Production signal → failure queue → triage → permanent eval case → gated fix. The bug can never silently return.
+
+### Audit, tamper-evident, regulator-ready
+
+```python
+from zolva import AuditLog, scorecard
+log = AuditLog("audit.db")     # hash-chained: edits, deletions, reordering all detectable
+log.attach(app)
+assert log.verify()
+print(scorecard(log).summary())  # SARR (Safe Automated Resolution Rate) + containment
+```
+
+### Synthetics, patrol every critical path
+
+```yaml
+# synthetics/repayment.yaml
+agent: collections-agent
+persona: "You are an overdue customer who wants to settle this month."
+goal: "customer obtains their dues amount and a valid repayment option"
+```
+
+A persona LLM converses with your *real* agent (staging tools); a judge grades the transcript. Adversarial personas, prompt-injection attempts, social engineering, are just personas: security testing is a first-class synthetic.
+
+### Human handover, one interface, your ticketing system
+
+```python
+from zolva import HandoverBackend, WebhookBackend
+app = AgentApp.from_config("agents/", handover=WebhookBackend(url, secret=hmac_secret))
+```
+
+Triggered by agent decision, guardrail violation, tool crash, provider failure, or the customer asking, one code path. Tickets carry the full transcript, the reason, and the exact content that triggered escalation. Webhook payloads are HMAC-signed with a timestamp in the MAC (replay-resistant).
+
+## Security posture
+
+- **Self-hosted by design**, nothing leaves your infrastructure except the LLM calls you configure; the bridge supports in-house gateways.
+- **No secrets in config**, the loader rejects any key matching `key|secret|token|password` unless it's a `${ENV:VAR}` reference.
+- **`yaml.safe_load` only; no `eval`/`exec`/`pickle` anywhere.**
+- **Tool contracts**, Pydantic-validated I/O with `extra="forbid"`; per-agent tool allowlists; `handoff` is a reserved name.
+- **Session isolation**, no cross-session context is ever assembled.
+- CI runs `bandit` and `pip-audit` on every commit.
+
+Found something? See [SECURITY.md](SECURITY.md), coordinated disclosure, 72-hour acknowledgement.
+
+## For AI coding agents
+
+Point your agent at [`llms.txt`](llms.txt) / [`llms-full.txt`](llms-full.txt), or hand it [`AGENTS.md`](AGENTS.md), exact setup, verification commands, and conventions, written to work first-try.
+
+## Status & roadmap
+
+**Beta.** Core runtime, all five plugins, and the CLI (`zolva validate | eval --gate | scorecard | triage | export-dataset`) are implemented and tested (105 tests, `mypy --strict`, 3-version CI matrix). Agents with a `guardrails:` field in their YAML get their policy attached automatically by `AgentApp.from_config`.
+
+Before 1.0:
+
+- Docs site at [zolva.ai](https://zolva.ai)
+- Voice/telephony channel adapters, ticketing-system handover backends (community welcome)
+- Auto-wiring `evals:` from agent YAML; judge model configured per policy
+
+Design docs: [`docs/specs/`](docs/specs/) · Full architecture, threat model, and competitive positioning included.
+
+## Contributing
+
+Every PR: `pytest -q && ruff check . && mypy` all green, tests first, conventional commits. See [AGENTS.md](AGENTS.md) for the full contract, it binds humans and AI contributors alike.
+
+## License
+
+[Apache-2.0](LICENSE)