## Home services: Inventory manager using Laravel

### Summary
A inventory manager blueprint for home services built with Laravel on Ample. Domain schema includes:
- **services** (sku, name, category, price_from, duration_estimate): Service catalog as SKUs.
- **parts_stock** (sku, delta, reason, moved_at): Parts and consumables movements.
- **jobs** (job_no, service_area, status, scheduled_for): Jobs as orders with status transitions.
- **job_lines** (job_no, sku, qty): Services and parts on a job.
- **events** (seq, record_type, record_id, kind, at): Application-owned history written in the same transaction.

**Public information** covers service catalog and pricing, service areas and hours, licensing, and insurance summary. Customer addresses and access instructions are personal data and should be kept out until handling is reviewed.

### Representative Queries
- Home services: Inventory manager using Laravel
- Where can I host Home services: Inventory manager built with Laravel?
- I need a genuinely specialized inventory manager workflow covering service areas, job materials, and field-job status.

### Resource Requirements
- Compute
- PostgreSQL
- S3-compatible object storage

### Infrastructure Requirements
1. **Compute**
   - **Status**: Verified
   - **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.

2. **Postgres**
   - **Status**: Verified
   - **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database.

3. **S3-compatible object storage**
   - **Status**: Verified
   - **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified.

### Framework
- Laravel

### Workload
- Inventory manager

### Industry
- Home services

### Release Status
- Published

### Support Status
- Verified

### Execution Status
- Ready

### Prerequisites
1. A Laravel project with appropriate installation commands.
2. A PostgreSQL driver reading DATABASE_URL.
3. Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables.
4. Review of which home services data classes may be handled.

### Workflow Steps
1. **Model the home services domain**: Create tables for services, parts_stock, jobs, job_lines, and 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.
4. **Workflow step 3**: Record an event per movement for history.
5. **Deploy**: Execute the synchronous deploy and read the result.
6. **Verify**: Run tests and acceptance checks for the workflow.

### Examples
- **Laravel pattern fixture**: Verified transactional workflows basis for this blueprint.

### Success Checks
1. App responds on its public URL.
2. Transactional-workflows self-test from the example.

### Limitations
- The technical basis and workflow were designed for this blueprint and were not executed as a separate application.
- Public content only until actual data-handling requirements have been reviewed.

### Cost Estimate
- **Monthly Amount**: 10.0 USD
- **Basis**: Size prices from pricing.toml
- **Components**:
  - **App server**: s-1vcpu-1gb
  - **Managed PostgreSQL database**: s-1vcpu-1gb
  
### Evidence Summary
- **Kind**: Canary run
- **Summary**: Laravel pattern fixture was deployed with checks passed.

### Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack, and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**