Compatibility & Dependencies

The Golden Rule

Every extension package depends only on lexigram and lexigram-contracts. No extension ever depends on another extension.

This rule keeps the dependency graph acyclic and ensures packages can be adopted independently. The core (lexigram) provides the DI container, Application abstraction, configuration, and logging. lexigram-contracts defines interface protocols that extensions implement.

Documented Exceptions

A small number of cross-extension dependencies exist where the functionality is inherently coupled:

Extension	Depends On	Reason
lexigram-events	lexigram-resilience	Event buses use retry and circuit breaker
lexigram-tasks	lexigram-resilience	Background jobs need retry and timeout policies
lexigram-ai-rag	lexigram-vector	RAG requires vector storage
lexigram-ai-agents	lexigram-ai-llm	Agents need an LLM client
lexigram-ai-memory	lexigram-ai-llm	Memory summarization uses the LLM
lexigram-ai-mcp	lexigram-ai-llm, lexigram-ai-agents	MCP exposes agents as tools

Note

These exceptions are explicitly managed and documented. Adding a new cross-extension dependency requires a design review to ensure it doesn’t create circular or tangled imports.

Python & Runtime

• Python version: 3.11+ required
• ASGI servers: Fully compatible with uvicorn, granian, and hypercorn
• Package manager: Works with pip, uv, and poetry

Known Constraints

Lexigram SQL

Requires an async database driver. Connection strings must use the async variant:

Database	Driver	Connection String
PostgreSQL	asyncpg	postgresql+asyncpg://user:pass@host/db
MySQL	aiomysql	mysql+aiomysql://user:pass@host/db
SQLite	aiosqlite	sqlite+aiosqlite:///path/to/db

Lexigram NoSQL — Wire Status

Backend	Status
MongoDB	Wired — provider is active and configurable
DynamoDB	Code exists but not wired — provider class written, not registered
Firestore	Code exists but not wired — provider class written, not registered

Lexigram Queue — Wire Status

Backend	Status
Memory / Redis / RabbitMQ / Kafka / SQS	Wired — fully configurable
Azure Service Bus / GCP Pub/Sub	Code exists but not wired — provider classes written, not registered

Lexigram Graph

Backend	Status
Neo4j	Wired — production-ready
In-memory	Wired — suitable for dev and testing

Optional Extras

Install backend-specific dependencies via extras:

Package	Extras
lexigram-sql	[postgres], [mysql], [sqlite]
lexigram-cache	[redis], [memcached]
lexigram-queue	[redis], [rabbitmq], [kafka], [sqs]
lexigram-search	[meilisearch], [elasticsearch], [typesense]
lexigram-storage	[s3], [gcs], [azure], [r2]
lexigram-vector	[pgvector], [qdrant], [pinecone]
lexigram-ai-llm	[openai], [anthropic], [google]

Maturity

All packages are alpha (0.1.x). Breaking changes may occur before the 1.0 release. We follow SemVer — breaking changes increment the minor version while below 1.0.

---

See Adoption Paths for a staged guide to integrating Lexigram packages.