erpclaw-fleet

Fleet operations are centralized through a single SQL action router performing CRUD operations on vehicles, assignments, fuel logs, and maintenance. It manages the end-to-end lifecycle using SQLite storage and an internal data access toolkit for validation and auditing.

Track maintenance and fuel logs by recording purchases and scheduling tasks through dedicated SQL actions. The system automatically generates cost and utilization reports while maintaining a consolidated activity audit trail across the four fleet tables.

Yes, driver assignments are managed with active status tracking. Creating or ending an assignment triggers automatic updates to the corresponding vehicle status, ensuring fleet availability data remains accurate across the SQLite database.

Yes, the erpclaw-lib dependency is required. It provides the foundational data access, auditing, and validation toolkit that the fleet domain actions rely on to ensure data integrity and conform to the repository's architectural standards.

Auditing works by routing all vehicle, assignment, fuel, and maintenance actions through a single router. This centralizes activity logs, providing a unified audit trail for all fleet lifecycle modifications and reporting outputs.

The single router architecture limits operations to SQLite storage and the four defined domain tables. Complex queries outside the vehicle, assignment, fuel, and maintenance domains require separate architectural components to execute.