### Equipment Rental: Order Tracking Using Next.js

#### Summary
A order tracking blueprint for equipment rental built with Next.js on Ample. Domain schema: 
- **Equipment** (sku, name, category, day_rate, serial_tracked): rental catalog; 
- **Stock Movements** (sku, unit_serial, delta, reason, moved_at): check-outs, returns and maintenance;  
- **Rentals** (rental_no, period_start, period_end, status): rentals with status transitions;  
- **Rental Lines** (rental_no, sku, unit_serial, rate): rental contents;  
- **Events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.  
Public information: equipment catalog and rates, availability calendar, deposit and insurance terms. Kept out of scope until handling is reviewed: renter identity documents, payment and deposit details. Identity verification and deposits are outside these flows; only availability and rental status are modeled.

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
- Equipment rental: order tracking using Next.js
- Where can I host Equipment rental: Order tracking built with Next.js?
- I need a genuinely specialized order tracking workflow covering asset serial numbers, availability windows and return status.

#### Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:s3-compatible-object-storage`

#### Infrastructure Requirements
1. **Compute**
   - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
   - Status: Verified  
   - [Path](/content/blueprints/equipment-rental/order-tracking/next-js/index.html)

2. **Postgres** 
   - 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.
   - Status: Verified  
   - [Path](/content/blueprints/equipment-rental/order-tracking/next-js/index.html)

3. **S3-Compatible Object Storage** 
   - Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified. 
   - Status: Verified  
   - [Path](/content/blueprints/equipment-rental/order-tracking/next-js/index.html)

#### Workflow Steps
1. Model the equipment rental domain: Create the tables equipment, stock_movements, rentals, rental_lines, events. Rental catalog lives in equipment; keep the sensitive classes (renter identity documents, payment and deposit details) 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. 
7. Verify: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the equipment rental workflow.

#### Cost Estimate
- Currency: USD
- Monthly Amount: $10.00
- Basis: Size prices from pricing.toml  (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.

#### Limitations
- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the equipment rental 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. Identity verification and deposits are outside these flows; only availability and rental status are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

#### Examples
- **Title**: Next.js pattern fixture 
 - **Description**: Verified transactional workflows basis for this blueprint. 
 - **Source**: tests/deploy-canaries/next-js-patterns

#### Next Actions
1. **Action**: Browse the catalog index
   - **Method**: GET
   - **Relative Path**: /v1/catalog

2. **Action**: Search published recipes by intent, stack and constraints
   - **Method**: POST
   - **Relative Path**: /v1/catalog/search

3. **Action**: Prepare a side-effect-free deployment plan for an authorized project
   - **Method**: POST
   - **Relative Path**: /v1/catalog/plan

4. **Action**: Read the existing agent authentication setup
   - **Method**: GET
   - **Relative Path**: /mcp/setup

5. **Action**: Browse Equipment rental
   - **Method**: GET
   - **Relative Path**: /v1/catalog/nodes/industry%3Aequipment-rental