### Home services: inventory manager using Next.js

**Summary:** A inventory manager blueprint for home services built with Next.js on Ample. Domain schema: 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: service catalog and pricing from, service areas and hours, licensing and insurance summary. Kept out of scope until handling is reviewed: customer addresses and access notes, payment details. Customer addresses and access instructions are personal data; keep them out until handling is reviewed. Technical basis verified on Next.js: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

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

**Resource Requirements:**
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

**Infrastructure Requirements:**
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

**Framework:** Next.js  
**Workload:** Inventory manager  
**Industry:** Home services  
**Release Status:** published  
**Support Status:** verified  
**Execution Status:** ready  
**Docs Only:** false

**Prerequisites:**
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which home services data classes may be handled at all; this blueprint models public information only

**Workflow Steps:**
1. **Model the home services domain**: Create the tables services, parts_stock, jobs, job_lines, events. Service catalog as SKUs lives in services; keep the sensitive classes (customer addresses and access notes, payment details) out of this schema.
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. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.

**Examples:**
- **Next.js pattern fixture**: Verified transactional workflows basis for this blueprint.

**Success Checks:**
- App responds on its public URL.
- Transactional-workflows self-test from the example.

**Limitations:**
- The technical basis was verified with the pattern fixture; the home services schema and workflow were not executed as a separate application.
- Customer addresses and access instructions are personal data; keep them out until handling is reviewed.
- Verified on the node-22 template at s-1vcpu-1gb; other sizes are unknown or unverified.

**Cost Estimate:**
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Components:**  
  - App server: s-1vcpu-1gb  
  - Managed PostgreSQL database: s-1vcpu-1gb  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.