## Home services: inventory manager using Django

### Summary  
A inventory manager blueprint for home services built with Django 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.

### Representative Queries  
- Home services: inventory manager using Django  
- Where can I host Home services: Inventory manager built with Django?  
- 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:**  
   - **Status:** verified  
   - **Summary:** 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:**  
   - **Status:** verified  
   - **Summary:** 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:**  
   - **Status:** verified  
   - **Summary:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Framework  
Django

### Workload  
Inventory manager

### Industry  
Home services

### Release Status  
published

### Support Status  
verified

### Execution Status  
ready

### Prerequisites  
- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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

### Tested Configuration  
- **Template:** python-3.12  
- **Runtime:** python  
- **Size:** s-1vcpu-1gb  
- **Install:** python3 -m pip install --target .ample/python -r requirements.txt  
- **Start:** PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

### Input Schema  
- **env:** Encrypted environment variables  
- **name:** App name  
- **path:** Project directory or ample.toml service  
- **release_command:** Migration command run before activation  
- **start:** Start command

### Workflow Steps  
1. **Model the home services domain:** Create the tables services, parts_stock, jobs, job_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. **Deploy:** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
6. **Verify:** Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.

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

### Success Checks  
1. **HTTP GET:** App responds on its public URL  
   - **Path:** /  
   - **Expect:** ample canary django patterns  
2. **HTTP GET:** transactional-workflows self-test from the example  
   - **Path:** /p/transactional-workflows  
   - **Expect:** see the pattern fixture checks

### Limitations  
- The technical basis (transactional workflows on Django) was verified with the pattern fixture.  
- No health, financial, privacy or other compliance claim is made.  
- Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.  
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.  
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

### Cost Estimate  
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Components:**  
   - **App server (s-1vcpu-1gb):** 5.0  
   - **Managed PostgreSQL database (s-1vcpu-1gb):** 5.0  
- **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.

### Evidence Summary  
- **Kind:** canary_run  
  - **Summary:** Django pattern fixture deployed on Ample.  
  - **Observed At:** 2026-09-20T03:31:44Z  
  - **Expires At:** 2027-03-19T03:31:44Z

### Next Actions  
- **Browse the catalog index:** GET /v1/catalog  
- **Search published recipes by intent, stack and constraints:** POST /v1/catalog/search  
- **Prepare a side-effect-free deployment plan for an authorized project:** POST /v1/catalog/plan  
- **Read the existing agent authentication setup:** GET /mcp/setup  
- **Browse Home services:** GET /v1/catalog/nodes/industry%3Ahome-services  
- **Browse Inventory manager:** GET /v1/catalog/nodes/workload%3Ainventory-manager  
- **Browse Django:** GET /v1/catalog/nodes/stack%3Aframework-django  
- **Browse Deploy web app:** GET /v1/catalog/nodes/intent%3Adeploy-web-app