# AI Architecture

## Independence Rule

AI capabilities are an **independent module family**. Business modules may consume AI via API/events but must remain functional when AI is disabled or unavailable.

## Boundaries

| AI may | AI must not |
| --- | --- |
| Suggest, classify, draft, route | Be the sole authority for money, compliance, or authorization |
| Read tenant-scoped knowledge bases | Cross tenant data |
| Emit assistance events | Bypass entitlement checks |

## Planned Module

`ai_assistant` — chat assistance, knowledge bases, handoff to humans. Database: `ai_assistant_db`. Feature prefix: `ai_assistant.*`.

## Provider Independence

Model providers are registered like any other provider ([provider-registry.md](../provider-registry.md)). Swapping vendors must not rewrite CRM/Accounting domain logic.

## Related Documents

- [Module Registry](../module-registry.md)
- [Compliance Architecture](compliance-architecture.md)
- [Phases / AI](../phases/AI/README.md)
- [Project Principles](../development/project-principles.md)
- [Enterprise / AI Development Framework](../ai-framework/README.md) (implementation process — distinct from this product AI architecture)
- [ADR-013](adr/ADR-013.md) · [ADR-018](adr/ADR-018.md) · [ADR-019](adr/ADR-019.md)
