## Hospitality: Vendor Portal Using Laravel

### Summary
A vendor portal 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
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information includes:
- room types, amenities and rates
- 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.

### Technical Basis
Verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

### Representative Queries
- Hospitality: vendor portal using Laravel
- Where can I host Hospitality: Vendor portal built with Laravel?
- I need a genuinely specialized vendor portal workflow covering property listings, service vendors and occupancy-related reporting.

### 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.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

### Workflow Steps
1. **Model the hospitality domain**: Create the tables room_types, inventory_movements, bookings, booking_lines, document_access.
2. **Workflow step 1**: Model vendors scoped to the agency with roles.
3. **Workflow step 2**: Authorize document access by vendor and role (401, 403 negative tests).
4. **Workflow step 3**: Store vendor documents in the private bucket.
5. **Workflow step 4**: Deploy and verify the negative tests and an authorized download.
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) and your own acceptance checks for the hospitality workflow.

### Examples
- **Laravel Pattern Fixture**: Verified private document library basis for this blueprint.

### Success Checks
- App responds on its public URL.
- Private-document-library self-test from the example.

### Limitations
- The technical basis verification was with the pattern fixture; the hospitality schema and workflow are an original design for this blueprint. No health, financial, or compliance claims are made.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server (s-1vcpu-1gb): $5.0
  - Managed PostgreSQL database (s-1vcpu-1gb): $5.0

### Evidence Summary
- **Canary run**: Laravel pattern fixture deployed on Ample; checks passed with a model for document access.

### Next Actions
1. Browse the catalog index
2. Search published recipes by intent, stack, and constraints.
3. Prepare a side-effect-free deployment plan for an authorized project.
4. Read the existing agent authentication setup.
5. Browse Hospitality.
6. Browse Vendor portal.
7. Browse Laravel.
8. Browse Deploy web app.
