# Roadmap

EloquentAiTools is read-only today. It is an AI reporting layer, not an agent that mutates your data.

That is a deliberate boundary, not a limitation waiting to be lifted by accident. Any write capability will be its own explicit, opt-in mechanism, never bolted invisibly onto `allowRead()`.

## Planned

- **Write tools to complete CRUD**: `Create`, `Update`, and `Delete` counterparts to today's read tool, built on the same resolver pipeline and the same config-driven whitelisting. A model exposing `allowRead()` will not silently gain write access.
- **Explicit joins**: a first-class request surface where the agent can declare join intent itself, instead of relying only on the current auto-derived joins from dotted relation-path columns.
- **`#[AiTool]`-attributed methods**: exposing an individual model method directly as its own AI tool, with its schema derived from the method signature or docblock instead of a generic query shape.

None of these change the core promise: every constraint the schema describes is still enforced at runtime, and nothing is exposed unless a model explicitly opts in.