## Hospitality: reporting dashboard using Laravel

### Summary
A reporting dashboard blueprint for hospitality built with Laravel 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 and rates from, property location and policies, events and dining. Kept out of scope until handling is reviewed: guest identity documents, payment details, stay history. Guest identity documents are sensitive; only availability and booking status are modeled here.

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

### Workflow Steps
1. **Model the hospitality domain**  
   Create the tables room_types, inventory_movements, bookings, booking_lines, exports. Room and package catalog lives in room_types; keep the sensitive classes (guest identity documents, payment details, stay history) out of this schema.
2. **Workflow step 1**  
   Model report definitions scoped to the agency.
3. **Workflow step 2**  
   Generate report artifacts from queries and store them with metadata.
4. **Workflow step 3**  
   Authorize downloads (401 without identity).
5. **Workflow step 4**  
   Deploy and verify an authorized export and the rejected anonymous request.
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/generated-downloads) and your own acceptance checks for the hospitality workflow.
   Command: `ample logs --kind build`

### Success Checks
- App responds on its public URL
  - Kind: http_get  
  - Path: /  
  - Expect: ample canary laravel patterns
- generated-downloads self-test from the example
  - Kind: http_get  
  - Path: /p/generated-downloads  
  - Expect: see the pattern fixture checks

### Limitations
- The technical basis (generated downloads on Laravel) 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.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - app server: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0
  - managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.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.