# Restaurants: Order Tracking Using Laravel

## Summary
A order tracking 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: menu with allergens and prices, locations, hours, and reservations contact, catering information.

## Technical Basis
Technical basis verified on Laravel: 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).

## 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 and Workload
- **Framework**: Laravel
- **Workload**: Order tracking

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

## 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 orders with explicit status transitions and order lines.
3. **Workflow step 2**: Apply status changes transactionally and record an event per change.
4. **Workflow step 3**: Expose status history to authorized callers only.
5. **Workflow step 4**: Deploy and verify history and conflict rejection.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   Command: `ample deploy . --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.
   Command: `ample logs  --kind build`

## Examples
- **Laravel pattern fixture**: Verified transactional workflows basis for this blueprint.
  - **Source Ref**: tests/deploy-canaries/laravel-patterns

## Success Checks
1. **App responds on its public URL**: Expect `ample canary laravel patterns`
2. **Transactional-workflows self-test from the example**: Expect `see the pattern fixture checks` at path `/p/transactional-workflows`

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

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.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.

## Next Actions
- **Browse the catalog index**:  `GET /v1/catalog`
- **Search published recipes**:  `POST /v1/catalog/search`
- **Prepare a deployment plan**:  `POST /v1/catalog/plan`
- **Read existing agent authentication setup**:  `GET /mcp/setup`
- **Browse Restaurants**:  `GET /v1/catalog/nodes/industry:restaurants`
- **Browse Order tracking**:  `GET /v1/catalog/nodes/workload:order-tracking`
- **Browse Laravel**:  `GET /v1/catalog/nodes/stack:framework-laravel`
- **Browse Deploy web app**:  `GET /v1/catalog/nodes/intent:deploy-web-app`

For more detailed documentation, refer to the [HTML Version](/content/blueprints/restaurants/order-tracking/laravel/index.html) or the [Markdown Version](/content/blueprints/restaurants/order-tracking/laravel.md).