### Hospitality: Reporting Dashboard Using Next.js

A reporting dashboard blueprint for hospitality built with Next.js on Ample.  
**Domain schema:**  
- **room_types** (sku, name, capacity, base_rate, amenities): Room and package catalog  
- **inventory_movements** (sku, date, delta, reason): Availability per date as stock movements  
- **bookings** (booking_no, check_in, check_out, status): Bookings with status transitions  
- **booking_lines** (booking_no, sku, nights, rate): Booking contents  
- **exports** (id, definition, object_key, row_count, generated_at, authorized_role): Generated artifacts and who may download them.

**Public information:** Room types, amenities, rates, property location and policies, events and dining.  
**Kept out of scope until handling is reviewed:** Guest identity documents, payment details, stay history.

Technical basis verified on Next.js: An export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

### Representative Queries
- Hospitality: reporting dashboard using Next.js  
- Where can I host Hospitality: Reporting dashboard built with Next.js?  
- I need a genuinely specialized reporting dashboard workflow covering property listings, service vendors and occupancy-related reporting.

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

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

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

### Success Checks
- **App responds on its public URL:** ample canary next js patterns  
- **Generated-downloads self-test from the example:** see the pattern fixture checks.

### Limitations
- The technical basis (generated downloads on Next.js) was verified with the pattern fixture; the hospitality 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. Guest identity documents are sensitive; only availability and booking status are modeled here.  
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

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

### Next Actions
- **Browse the catalog index**: `GET /v1/catalog`  
- **Search published recipes by intent, stack and constraints**: `POST /v1/catalog/search` with body {"limit":5,"query":"Hospitality: reporting dashboard using Next.js"}  
- **Prepare a side-effect-free deployment plan for an authorized project**: `POST /v1/catalog/plan` with body {"inputs":{},"projectId":,"recipeId":"page:blueprints:hospitality:reporting-dashboard:next-js","recipeRevision":"r1"}