## Property management: reporting dashboard using Laravel

### Summary
A reporting dashboard blueprint for property management built with Laravel on Ample. Domain schema:
- **listings** (reference, address, unit, rent, publishing_status, agency_id): rental listings with publishing status;
- **agencies** (name, license_number, portfolio_size): management offices;
- **maintenance_vendors** (name, trade, agency_id, status): vendors per office;
- **reports** (agency_id, period, object_key, generated_at): portfolio reports per office;
- **exports** (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them.

### Public information
Available rentals, office contacts, application process.

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

### Resource Requirements
- **Compute**
- **Postgres**
- **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.

### Workflow Steps
1. **Model the property management domain**: Create the tables listings, agencies, maintenance_vendors, reports, exports. Rental listings with publishing status live in listings; keep the sensitive classes (tenant identity and payment history, inspection reports with personal data) 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.
7. **Verify**: Run the pattern self-test(s) from the example (/p/generated-downloads) and your own acceptance checks for the property management workflow.

### Examples
- **Laravel pattern fixture**: Verified generated downloads basis for this blueprint.  
  Source Reference: `tests/deploy-canaries/laravel-patterns`

### Success Checks
1. App responds on its public URL.
2. Generated-downloads self-test from the example.

### Limitations
- The technical basis (generated downloads on Laravel) was verified with the pattern fixture; the property management 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. Tenant data is personal and often regulated; only published listings and office-scoped reporting are modeled.

### 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: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0.
    - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0.

### Evidence Summary
- **Type**: Canary run.
- **Summary**: Laravel pattern fixture deployed on Ample; the generated downloads checks passed: 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).

### Next Actions
- Browse the catalog index.
- Search published recipes by intent, stack and constraints.
- Prepare a side-effect-free deployment plan for an authorized project.