## The short version

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

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): verified (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](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Before you start

- 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 restaurants data classes may be handled at all; this blueprint models public information only

## How to do it

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.
   
   ```
   ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   ```

7. **Verify**  
   Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the restaurants workflow.

```
   ample logs <deployment_id> --kind build
   ```

## Tested examples

- **Next.js pattern fixture** (`tests/deploy-canaries/next-js-patterns`): Verified transactional workflows basis for this blueprint.

## How to know it worked

- App responds on its public URL (`/` on the live URL, expect ample canary next js patterns)
- Transactional-workflows self-test from the example (`/p/transactional-workflows` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- App server x1 `s-1vcpu-1gb`: 5.00 USD
- Managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- Canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); 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). The blueprint's Restaurants schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.

## Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the API origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the API origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the API origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the API origin; authentication not required, approval not required)
- Browse Restaurants (`GET /v1/catalog/nodes/industry%3Arestaurants` on the API origin; authentication not required, approval not required)
- Browse Product catalog (`GET /v1/catalog/nodes/workload%3Aproduct-catalog` on the API origin; authentication not required, approval not required)
- Browse Next.js (`GET /v1/catalog/nodes/stack%3Aframework-next-js` on the API origin; authentication not required, approval not required)
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the API origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status

Recipe `page:blueprints:restaurants:product-catalog:next-js`. Revision r1.

Release **published**
Support **verified**
Execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/blueprints/restaurants/product-catalog/next-js/index.html) | [Markdown](/content/blueprints/restaurants/product-catalog/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Arestaurants%3Aproduct-catalog%3Anext-js)