# Restaurants: Product Catalog using Laravel

## Summary
A product catalog blueprint for restaurants built with Laravel on Ample.  
Domain schema:  
- **menu_items** (sku, name, section, price, allergens, active): the menu as a SKU catalog;  
- **stock_movements** (sku, delta, reason, moved_at): ingredient and prepared-item stock;  
- **orders** (order_no, service_type, status, placed_at): dine-in, pickup, and delivery orders;  
- **order_lines** (order_no, sku, qty, modifiers): order contents;  
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

Public information includes: menu with allergens and prices, locations, hours and reservations contact, catering information. Kept out of scope until handling is reviewed: customer contact and payment details, staff schedules. Allergen information must be kept accurate by the operator; nothing here validates food-safety claims.

## 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 (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which restaurant data classes may be handled at all; this blueprint models public information only

## Framework
**Framework**: Laravel  
**Workload**: Product catalog  
**Industry**: Restaurants  
**Release Status**: published  
**Support Status**: verified  
**Execution Status**: ready

## Resource Requirements
- **Compute**:  Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Workflow Steps
1. **Model the restaurants domain**:  Create the tables menu_items, stock_movements, orders, order_lines, events. The menu as a SKU catalog lives in menu_items; keep the sensitive classes (customer contact and payment details, staff schedules) out of this schema.
2. **Workflow step 1**:  Model the SKU catalog with versioned updates.
3. **Workflow step 2**:  Record every catalog change as an event in the same transaction.
4. **Workflow step 3**:  Reject stale concurrent updates.
5. **Workflow step 4**:  Deploy and verify history and conflict handling.
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 restaurants workflow.

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

## Success Checks
- *App responds on its public URL*  
  Path: `/`  
  Expect: ample canary Laravel patterns  
- *Transactional-workflows self-test from the example*  
  Path: `/p/transactional-workflows`  
  Expect: see the pattern fixture checks

## Limitations
- The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the restaurants 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. Allergen information must be kept accurate by the operator; nothing here validates food-safety claims.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 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
- **Monthly Amount**: $10.00  
  - **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
  - **Components**:  
    - App server: size `s-1vcpu-1gb`, quantity: 1.0, monthly amount: $5.00  
    - Managed PostgreSQL database: size `s-1vcpu-1gb`, quantity: 1.0, monthly amount: $5.00  
- **Note**: Always-on monthly price of tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Canary Run**: Laravel pattern fixture deployed on Ample; the transactional workflows checks passed: 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).
  - **Observed At**: 2026-09-20T20:36:21Z

## Next Actions
1. **Browse the catalog index** (GET: /v1/catalog)  
2. **Search published recipes by intent, stack and constraints** (POST: /v1/catalog/search)  
3. **Prepare a side-effect-free deployment plan for an authorized project** (POST: /v1/catalog/plan)  
4. **Read the existing agent authentication setup** (GET: /mcp/setup)  
5. **Browse Restaurants** (GET: /v1/catalog/nodes/industry%3Arestaurants)  
6. **Browse Product catalog** (GET: /v1/catalog/nodes/workload%3Aproduct-catalog)  
7. **Browse Laravel** (GET: /v1/catalog/nodes/stack%3Aframework-laravel)  
8. **Browse Deploy web app** (GET: /v1/catalog/nodes/intent%3Adeploy-web-app)