intagrin 0.1.0__tar.gz

intagrin-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 IntaGrin Team
+
+   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.

intagrin-0.1.0/PKG-INFO

@@ -0,0 +1,350 @@
+Metadata-Version: 2.4
+Name: intagrin
+Version: 0.1.0
+Summary: The definitive Python framework for enterprise AI agents and autonomous swarms.
+Author-email: Anoop P S <hello@intagrin.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/intagrin/intagrin
+Project-URL: Documentation, https://docs.intagrin.com/
+Project-URL: Repository, https://github.com/intagrin/intagrin
+Project-URL: Issues, https://github.com/intagrin/intagrin/issues
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer>=0.12.0
+Requires-Dist: rich>=13.7.0
+Requires-Dist: pydantic>=2.7.0
+Requires-Dist: litellm>=1.35.0
+Requires-Dist: mcp>=1.0.0
+Requires-Dist: ruamel.yaml>=0.18.6
+Requires-Dist: opentelemetry-sdk>=1.24.0
+Requires-Dist: opentelemetry-api>=1.24.0
+Requires-Dist: Jinja2>=3.1.3
+Requires-Dist: python-dotenv>=1.0.1
+Requires-Dist: fastapi>=0.100.0
+Requires-Dist: uvicorn>=0.23.0
+Requires-Dist: gunicorn>=21.2.0
+Requires-Dist: alembic>=1.13.0
+Requires-Dist: sqlalchemy>=2.0.0
+Provides-Extra: postgres
+Requires-Dist: psycopg[binary,pool]>=3.1.0; extra == "postgres"
+Provides-Extra: redis
+Requires-Dist: redis>=5.0.0; extra == "redis"
+Dynamic: license-file
+
+<p align="center">
+    <img src="https://raw.githubusercontent.com/intagrin/intagrin/main/docs/assets/logo3.png" alt="IntaGrin Logo" width="200"/>
+</p>
+
+<p align="center">
+    <b>A declarative framework for building multi-agent LLM systems in YAML</b>
+</p>
+
+<p align="center">
+    <img src="https://img.shields.io/badge/version-0.1.0-blue.svg" alt="Version 0.1.0"/>
+    <a href="./LICENSE">
+        <img src="https://img.shields.io/badge/License-Apache%202.0-success.svg" alt="License"/>
+    </a>
+    <img src="https://img.shields.io/badge/status-active-brightgreen.svg" alt="Active"/>
+</p>
+
+> **Status:** IntaGrin is under active development.
+
+## 🎯 Why IntaGrin?
+
+- **Declarative, not programmatic.** Routing, guardrails, and memory live in `ai.yaml`, not in
+  hand-wired Python graph code or agent/crew objects. Less boilerplate to write and review — and,
+  increasingly relevant, easier for an AI coding assistant to generate and validate than a
+  sprawling graph definition, since the whole surface is a schema-checked config file instead of
+  arbitrary code.
+- **Governance built in, not bolted on.** Circuit breakers with an honest bounded/unbounded cost
+  accounting, human-in-the-loop approval scoped to the exact call that needs it (not just the
+  tool), a content-provenance guardrail for the "lethal trifecta" pattern (untrusted input +
+  data access + a way to exfiltrate), and sandboxed code execution — all declared in config, not
+  assembled by hand from separate libraries.
+- **Static verification before runtime.** `inta verify` catches routing cycles, unbounded cost
+  paths, and misconfigured guardrails before you ever run the agent — and tells you exactly which
+  parts of your graph it *can't* verify (semantic routing, dynamic agent spawning), instead of a
+  blanket "all good."
+- **Honesty over marketing.** Every tool in this repo says what it doesn't cover, not just what it
+  does — the fuzzer calls its own checks "keyword-heuristic," the sandbox tool documents that it
+  isn't a filesystem/network security boundary. A claim only ships if the code actually backs it.
+
+## Summary
+
+**IntaGrin** is a declarative framework for building multi-agent LLM systems. Instead of wiring
+routing logic in Python (as you would with a hand-built graph), you describe agents, handoffs,
+tools, and guardrails in a single `ai.yaml` file, and the runtime engine executes that
+configuration directly.
+
+It includes a static verifier for the parts of your routing graph that *are* statically
+analyzable (handoffs and deterministic routers), circuit breakers for cost/loop protection,
+Pydantic-backed schema validation for shared state and structured agent output, an adversarial
+prompt fuzzer, and a diagnostics command that runs real test batches and reports the metrics it
+actually measured. Where a mechanism has real limits — semantic (LLM-routed) handoffs can't be
+statically verified, the fuzzer's defense checks are keyword-heuristic rather than a full security
+audit — the tool says so directly rather than rounding up.
+
+---
+
+## 🌟 Core Capabilities
+
+### 1. Spec-Driven Architecture (Natural Language to Production)
+Describe the desired swarm topology in a plain-English `blueprint.md` file, then run `inta compile`
+to generate a structured `ai.yaml` from it. This is meant to reduce hand-wiring routing logic in
+Python for common patterns — it's a starting point to review and edit, not a black box.
+
+### 2. Argument & Schema Self-Healing
+When a tool call arrives with malformed JSON or arguments that fail validation, IntaGrin retries by
+asking a fast corrector model to fix the arguments (up to 2 attempts) before surfacing the error.
+The same mechanism validates structured agent responses against a `response_schema` and shared
+state writes against a `state_schema` — both are real Pydantic models loaded and validated at
+runtime, not just declared. Healing is scoped to fixing arguments/output in memory; it never
+modifies source code, prompts, or your declared routing.
+
+### 3. Reducing Tool-Schema Bloat
+`lazy_load_tools: true` on an agent uses a fast model call to select which tool schemas are
+actually relevant to the current conversation before sending them to the primary model — useful
+when an agent has many tools but only needs a few per turn. That selection call is debounced: an
+unchanged recent-message trajectory reuses the last selection instead of re-querying the router
+model every tool-call round. Building the `ai.yaml`/prompt/tool-file structure with an AI coding
+assistant also tends to need less back-and-forth than wiring the same logic in a general-purpose
+graph framework, since there's less boilerplate to review.
+
+### 4. Static Verification & Adversarial Fuzzing
+`inta verify` performs real cycle detection across declared handoffs and deterministic routers,
+reports delegation depth/turn bounds, and gives an explicit worst-case cost accounting that lists
+which cost paths are bounded and which aren't. Self-healing retries, memory-compression input
+size, and per-turn parallel tool calls are all capped by dedicated `circuit_breakers` settings
+(`max_corrector_tokens`, `max_compression_batch_messages`, `max_parallel_tool_calls_per_turn`) —
+the report shows their configured bound rather than a blanket "unbounded."
+Semantic (`auto_route`) handoffs are an LLM decision at runtime and are reported separately as
+non-deterministic, bounded only by the hard turn cap, not by graph acyclicity. `inta fuzz` generates
+adversarial prompts (prompt injection, PII extraction, boundary overflows) and runs them against
+your live agents; its pass/fail check is keyword-heuristic today, so treat the score as a smoke test
+rather than a substitute for a real security review.
+
+### 5. Observability & Diagnostics
+`inta monitor` launches a local SSE-backed dashboard showing live agent handoffs, tool calls, and
+token/cost telemetry as your swarm runs. `inta diagnose` runs a batch of real requests — your
+`tests/evals.yaml` if present, or a small generated probe battery otherwise — and reports metrics
+computed from those actual runs: context-window utilization, tool error rate, cost, and latency,
+with a rules-based explanation of whichever metric crossed its threshold.
+
+---
+
+## 🛠️ The AI-Native Developer Experience
+
+IntaGrin provides a unified, deeply integrated Command Line Interface (CLI) that manages the entire lifecycle of an AI application.
+
+### Project Initialization & Compilation
+* `inta new` (or `init`) — Scaffold a new IntaGrin project structure.
+* `inta compile` — Compile a natural language `blueprint.md` into a diff-merged `ai.yaml` configuration.
+* `inta import` — Import an OpenAPI/Swagger spec and generate a starting `ai.yaml` with tools wired to its endpoints.
+* `inta copilot` — Generate IDE rule/skill files (e.g. `.cursor/rules/`) describing IntaGrin's conventions to your AI coding assistant.
+* `inta architect` — Launch a built-in AI assistant to iteratively refactor and modify your swarm architecture directly from the terminal.
+
+### Quality Assurance & Security
+* `inta fuzz` — Generates adversarial prompts (prompt injection, PII extraction, boundary overflows) and runs them against your live agents. Pass/fail detection is keyword-heuristic — a useful smoke test, not a substitute for a real security review.
+* `inta verify` — Static cycle detection across handoffs and deterministic routers, delegation depth/turn bounds, and an explicit worst-case cost accounting that lists what's bounded vs. not.
+* `inta simulate --config <candidate.yaml>` — Shadow Replay: re-evaluates a candidate `ai.yaml`'s routers, circuit breakers, and `requires_approval` flags against real checkpointed sessions — zero new LLM calls, zero re-executed tools — and reports what would actually change before you deploy it. Limited to config changes that can't alter what the LLM itself generates (prompts/models/tool identity); anything else is reported as not-yet-simulatable rather than guessed at.
+* `inta synth` — Generates boundary-case test inputs (numeric/string edge cases, handoff transitions) from your tool signatures and agent config into `tests/evals.yaml`.
+* `inta eval` — Runs the cases in `tests/evals.yaml` against your live agents and checks expected agent/tool/output assertions, with optional LLM-as-judge scoring.
+* `inta tune` — Iteratively repairs failing prompts against `tests/evals.yaml`. Snapshots every prompt it touches first and rolls back to the original if it doesn't converge within the iteration limit.
+
+### Runtime, Debugging, & Observability
+* `inta dev` — Launch the local developer environment with hot-reloading.
+* `inta run <workflow>` — Execute a named autonomous workflow directly from the terminal.
+* `inta monitor` — Launch the local Web Dashboard to watch agent handoffs, tool calls, and token/cost telemetry live over SSE.
+* `inta diagnose` — Run a batch of real requests (your `tests/evals.yaml`, or a small generated probe battery) and report computed metrics: context-window utilization, tool error rate, cost, and latency.
+* `inta replay` — Rewind and replay the recorded sequence of events from a past checkpointed session.
+
+### Deployment
+* `inta export` — Export your default agent's prompt and local tools (with a real tool-calling loop) to a standalone FastAPI application with no IntaGrin runtime dependency. Single-agent scope — handoffs, routers, guardrails, and HITL aren't reproduced; keep using `inta serve` for the full swarm.
+* `inta deploy` — Generate a `Dockerfile` and `docker-compose.yml` for the project, running as a non-root user.
+* `inta worker` — Start a background worker that pulls jobs from a local SQLite queue (atomic, concurrency-safe) or a Redis queue if `--redis-url` is configured. Tool connections and the RAG index are built once and reused across every job, not rebuilt per job.
+* `inta serve` — Start the FastAPI production server (SSE streaming, `/resume` for human-in-the-loop, `/ws/voice`). MCP connections, tool schemas, and the RAG index are pooled per project across requests — see [Runtime Resource Pooling](./docs/04_Production_Deployment.md#runtime-resource-pooling).
+
+---
+
+## 🚀 Getting Started
+
+### 1. Installation
+
+```bash
+pip install intagrin      # or: uv add intagrin
+```
+
+If a project sets `memory.type: postgres` or `memory.type: redis`, install the matching extra —
+these client libraries are optional (not pulled in by default) so a plain SQLite/in-process project
+stays lightweight:
+```bash
+uv sync --extra postgres   # or: pip install -e ".[postgres]"
+uv sync --extra redis      # or: pip install -e ".[redis]"
+```
+
+### 2. Scaffold Your Project
+Initialize your project scaffolding and navigate into it:
+```bash
+inta new my-first-swarm
+cd my-first-swarm
+```
+
+### 3. The Coding Agent Workflow (The "IntaGrin Way")
+Because IntaGrin's routing, tools, and guardrails are declared in `ai.yaml` rather than wired in
+Python, an AI coding assistant working in this repo generally has less boilerplate to read and
+write per agent than it would with a hand-built Python graph. We recommend building your
+application using the **Spec-Driven** approach.
+
+Instead of writing code manually, simply describe what you want your swarm to do in plain English inside `blueprint.md`:
+
+```markdown
+# blueprint.md
+
+## Vision
+Build a highly resilient Customer Support Swarm that processes incoming tickets, handles billing, and seamlessly escalates complex issues.
+
+## Constraints
+- The Billing Agent must strictly require human approval before issuing any Stripe refunds.
+- Simple triage must use a lightweight model (e.g. Gemini 1.5 Flash) to save costs.
+- The swarm must never enter an infinite loop if a refund fails.
+
+## Agents
+1. **Triage Agent:** Reads incoming emails and routes them based on the customer's intent.
+2. **Billing Agent:** Securely interfaces with the Stripe API to process refunds.
+3. **Human Escalation:** A fallback agent that halts the swarm if an API error occurs.
+```
+
+Now, compile your English blueprint into a production-ready Swarm Architecture using the IntaGrin compiler:
+```bash
+inta compile
+```
+*(Your AI coding assistant — or IntaGrin's built-in compiler — reads the Markdown and generates a structured `ai.yaml`. Review the output; treat it as a first draft, not a final architecture.)*
+
+### 4. Launch & Monitor
+Start the live visual dashboard and run your swarm!
+```bash
+inta monitor
+inta run daily_audit
+```
+Open `http://localhost:3000` to watch your swarm light up in real-time.
+
+---
+
+## 🏗️ Architectural Paradigm: Declarative Orchestration
+
+IntaGrin gives you both routing styles under one config, and you choose per agent: **deterministic
+routers** (a Python condition evaluated against state, no LLM call involved) for logic you want
+statically verifiable, and **LLM-driven handoffs** (`transfer_agent`) for decisions that genuinely
+need the model's judgment. State reducers, tool scoping, and circuit breakers are all declared in
+the same `ai.yaml`.
+
+<p align="center">
+    <img src="https://raw.githubusercontent.com/intagrin/intagrin/main/docs/assets/diagram.png" alt="IntaGrin Logo" width="600"/>
+</p>
+
+<p align="center">
+    <img src="https://raw.githubusercontent.com/intagrin/intagrin/main/docs/assets/workflow.png" alt="IntaGrin Logo" width="600"/>
+</p>
+
+```yaml
+# ai.yaml
+name: "SaaS Customer Support Swarm"
+version: "1.0"
+default_agent: "TriageAgent"       # Entry point for the Swarm
+
+circuit_breakers:
+  max_usd_cost_per_session: 0.50   # Hard stop if API costs exceed 50 cents
+  max_handoffs_per_session: 3      # Caps handoff ping-pong (defaults to 25 if unset)
+
+reducers:
+  - key: "customer_context"
+    strategy: "deep_merge"         # Automatically merge CRM data into state
+
+model:
+  primary: "openai/gpt-4o"
+  fallback: "gemini/gemini-3.5-flash"
+
+agents:
+  TriageAgent:
+    description: "Reads incoming support tickets and classifies the user intent."
+    lazy_load_tools: true          # Cost Cutter: Dynamically injects only needed tools
+    model_override: "gemini/gemini-3.5-flash-lite"  # Cost Cutter: Use cheap model for simple triage
+    routers:
+      - target: BillingAgent
+        condition: "'refund' in intent"
+      - target: TechnicalAgent
+        condition: "'bug' in intent"
+    tools:
+      - name: "zendesk_mcp"
+        type: "mcp"
+        command: "npx"
+        args: ["@modelcontextprotocol/server-zendesk"]
+      - name: "fetch_user_profile"
+        module: "tools.crm"
+
+  BillingAgent:
+    description: "Handles subscription changes and issues refunds."
+    tools:
+      - name: "stripe_mcp"
+        type: "mcp"
+        command: "npx"
+        args: ["@modelcontextprotocol/server-stripe"]
+      - name: "issue_refund"
+        module: "tools.billing"
+        requires_approval: true    # Enterprise Safety: Halts for Human-in-the-Loop approval before sending money!
+```
+
+---
+
+## 📖 Full Documentation
+
+The hosted docs site — **<https://docs.intagrin.com/>** — covers the `ai.yaml` reference,
+tools/MCP integration, RAG, human-in-the-loop, deployment, and the API. The [`docs/`](./docs) folder
+in this repository is the source those pages are built from, and is the source of truth for what
+the current code does if the two ever drift.
+
+---
+
+## 🧪 Testing This Repository
+
+```bash
+uv run pytest tests/       # full suite (SQLite/mocked backends only, no external services needed)
+uv run ruff check .        # lint, matches CI
+```
+
+The Postgres and Redis checkpointer backends additionally have real-instance integration tests
+(`tests/test_memory_integration.py`, `tests/test_auto_migrate_postgres.py`) that are **not** part
+of the default suite above — they skip themselves cleanly when no instance is reachable. To run
+them against local Docker containers:
+```bash
+uv sync --extra postgres --extra redis
+docker compose -f docker-compose.test.yml up -d
+uv run pytest tests/test_memory_integration.py tests/test_auto_migrate_postgres.py -q
+docker compose -f docker-compose.test.yml down
+```
+
+---
+
+## 📚 Example Use Cases
+
+These are illustrative patterns — designs you'd build with IntaGrin's handoffs/tools/MCP, not
+templates that ship with the framework:
+
+| Example Swarm | Description |
+| :--- | :--- |
+| **Autonomous DevOps Engineer** | Monitors Datadog alerts, pulls distributed traces, and safely restarts Kubernetes pods via MCP servers. |
+| **Customer Support Triage** | An asynchronous swarm that routes complex tickets, validates Stripe refunds, and drafts personalized apology emails. |
+| **Cybersecurity SOC Analyst** | An event-driven swarm that ingests real-time threat intel, cross-references CVE databases, and executes firewall IP quarantines. |
+
+---
+
+> [!NOTE]
+> **No Vendor Lock-In (for the parts it exports)**
+> IntaGrin is open-source (Apache 2.0). `inta export` compiles your project's **default agent** —
+> its prompt and local tools, with a real tool-calling loop, no IntaGrin import required at
+> runtime — into a single standalone FastAPI file. This is a single-agent export: handoffs,
+> delegations, routers, circuit breakers, guardrails, and human-in-the-loop approval are not
+> reproduced, and MCP/OpenAPI tools aren't included either (no live connection is possible in one
+> dependency-free file). For a real multi-agent swarm, keep running `inta serve` — `inta export`
+> is for walking away with your single busiest agent, not the whole framework.