# Equipment rental: inventory manager using Laravel

## Summary
A inventory manager blueprint for equipment rental built with Laravel on Ample. Domain schema includes:
- **equipment** (sku, name, category, day_rate, serial_tracked): rental catalog.
- **stock_movements** (sku, unit_serial, delta, reason, moved_at): check-outs, returns and maintenance.
- **rentals** (rental_no, period_start, period_end, status): rentals with status transitions.
- **rental_lines** (rental_no, sku, unit_serial, rate): rental contents.
- **events** (seq, record_type, record_id, kind, at): application-owned history.

## Representative Queries
- Equipment rental: inventory manager using Laravel
- Where can I host Equipment rental: Inventory manager built with Laravel?
- I need a genuinely specialized inventory manager workflow covering asset serial numbers, availability windows and return status.

## Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:s3-compatible-object-storage`

## Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs. 
2. **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials.

## Framework Details
- **Framework**: Laravel
- **Workload**: Inventory manager
- **Industry**: Equipment rental
- **Release Status**: Published
- **Support Status**: Verified
- **Execution Status**: Ready

## Prerequisites
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template).
- A PostgreSQL driver reading DATABASE_URL.
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables.

## Workflow Steps
1. **Model the equipment rental domain**: Create the tables equipment, stock_movements, rentals, rental_lines, events.
2. **Workflow step 1**: Model SKUs and stock movements; derive stock from movements.
3. **Workflow step 2**: Apply movements transactionally with an optimistic version check on the SKU.
4. **Workflow step 3**: Record an event per movement for history.
5. **Workflow step 4**: Deploy and verify history and rejected stale updates.
6. **Deploy**: Run the synchronous deploy once and read the result.
7. **Verify**: Run pattern self-test(s) for the equipment rental workflow.

## Limitations
- The equipment rental schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy, or other compliance claim is made. Only availability and rental status are modeled.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: s-1vcpu-1gb (monthlyAmount: 5.0)
  - Managed PostgreSQL database: s-1vcpu-1gb (monthlyAmount: 5.0)

## Evidence Summary
- **Summary**: Laravel pattern fixture deployed on Ample; the transactional workflows checks passed.
- **Last Verified At**: 2026-09-20T20:36:21Z

## Next Actions
- **Browse the catalog index**: /v1/catalog
- **Search published recipes**: /v1/catalog/search
- **Prepare deployment plan**: /v1/catalog/plan
