# QuadKit

> Oridecon Labs is an AI product engineering studio designing and building software products, and the team behind QuadKit — an async-first, contract-driven Python framework for coding agents. Its open-source catalog of 18 packages is published at 0.0.50 (Apache 2.0, Python 3.11+).

QuadKit is alpha (0.0.x), public release 0.0.50, Apache 2.0 licensed, Python 3.11+. Prefer protocols over concrete classes. Pin `>=0.0.50,<0.1`. Package-boundary rules vary by family; regular extension independence has tracked exceptions and composite packages have separate contracts.

# Per-package LLM indexes

One file per package so a SQL, agent, or workflow task does not load the whole catalog. Rules: https://oridecon.dev/agents.md · Full index: https://oridecon.dev/llms.txt

## Foundation

- [quadkit](https://oridecon.dev/llms/quadkit.txt) — Async-first core: the DI container, application lifecycle, providers, modules, typed config, and the Result model.
- [quadkit-contracts](https://oridecon.dev/llms/quadkit-contracts.txt) — Protocols, shared types, and the exception hierarchy — zero runtime dependencies beyond typing-extensions.

## Web & HTTP

- [quadkit-web](https://oridecon.dev/llms/quadkit-web.txt) — The async web layer: controllers with signature-based binding, middleware pipelines, a Result-to-HTTP bridge, and OpenAPI.
- [quadkit-http](https://oridecon.dev/llms/quadkit-http.txt) — HTTP client with typed Result errors, retries, timeouts, and a pluggable transport for calling other services.

## AI & Agents

- [quadkit-ai-llm](https://oridecon.dev/llms/quadkit-ai-llm.txt) — Unified async LLM layer: streaming completions, structured outputs, embeddings, cost attribution, and multi-provider adapters.
- [quadkit-ai-agents](https://oridecon.dev/llms/quadkit-ai-agents.txt) — Typed agent loops, `@tool` functions, handoffs, human-in-the-loop checkpoints, and structured execution traces.
- [quadkit-ai-mcp](https://oridecon.dev/llms/quadkit-ai-mcp.txt) — Model Context Protocol servers and clients: stdio and HTTP/SSE transports, tool/resource/prompt bridges, and DI wiring.

## Data

- [quadkit-sql](https://oridecon.dev/llms/quadkit-sql.txt) — Async SQL repositories: typed rows, migrations, connection pooling, and a repository base over SQLAlchemy and asyncpg.
- [quadkit-cache](https://oridecon.dev/llms/quadkit-cache.txt) — Cache primitives: a Cache protocol, in-memory and Redis backends, stampede-safe single-flight helpers, and TTL invalidation.
- [quadkit-storage](https://oridecon.dev/llms/quadkit-storage.txt) — Artifact storage: a BlobStore protocol, local and S3 backends, content-addressed keys, and signed URL helpers.

## Events & Notifications

- [quadkit-events](https://oridecon.dev/llms/quadkit-events.txt) — Event bus, outbox publishing, durable subscriptions, and a timeline/replay API for auditing what happened.
- [quadkit-notification](https://oridecon.dev/llms/quadkit-notification.txt) — Multi-channel notifications: email, SMS, push, Slack, and webhook delivery with templates, user preferences, and digest batching.

## Infra & Workflows

- [quadkit-tasks](https://oridecon.dev/llms/quadkit-tasks.txt) — Background tasks: a queue, worker pools, retries with backoff, schedules, and an HTTP console for observing runs.
- [quadkit-workflow](https://oridecon.dev/llms/quadkit-workflow.txt) — Durable workflows, DAG pipelines, state machines, human approval gates, and compensating sagas with checkpoint/resume.
- [quadkit-monitor](https://oridecon.dev/llms/quadkit-monitor.txt) — Observability: counters, histograms, structured logs, health/readiness probes, and a metrics endpoint.

## Security

- [quadkit-auth](https://oridecon.dev/llms/quadkit-auth.txt) — Authentication and authorization: API keys, MFA, RBAC, session stores, and login flows wired through the DI container.

## Tooling

- [quadkit-cli](https://oridecon.dev/llms/quadkit-cli.txt) — The quadkit command line: project scaffolding, generators, a smart runner, and admin commands.
- [quadkit-testing](https://oridecon.dev/llms/quadkit-testing.txt) — Test harnesses, fakes, and fixtures that boot the real application in-process.