### Restaurants: product catalog using Next.js

A product catalog blueprint for restaurants built with Next.js 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: 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. 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
- Restaurants: product catalog using Next.js
- Where can I host Restaurants: Product catalog built with Next.js?
- I need a genuinely specialized product catalog workflow covering menu availability, ingredient records and order status.

#### 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.

#### Cost Estimate
- Monthly Amount: **$10.00** USD
- Components:
  - **App server**: size s-1vcpu-1gb, quantity 1 ($5.00)
  - **Managed PostgreSQL database**: size s-1vcpu-1gb, quantity 1 ($5.00)
- 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.

#### Limitations
- The technical basis (transactional workflows on Next.js) 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 node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

#### Evidence Summary
- **Canary Run**: Next.js pattern fixture deployed on Ample; the transactional workflows checks passed.

#### Next Actions
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes**: `POST /v1/catalog/search`
- **Prepare deployment plan**: `POST /v1/catalog/plan` 
- **Read existing authentication setup**: `GET /mcp/setup`
- **Browse Restaurants**: `GET /v1/catalog/nodes/industry%3Arestaurants`
- **Browse Product catalog**: `GET /v1/catalog/nodes/workload%3Aproduct-catalog`
- **Browse Next.js**: `GET /v1/catalog/nodes/stack%3Aframework-next-js`
- **Browse Deploy web app**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`

#### Technical Basis
- **Framework**: Next.js
- **Workload**: Product catalog
- **Industry**: Restaurants
- **Release Status**: Published
- **Support Status**: Verified
- **Execution Status**: Ready

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