# Property management: public directory using Next.js

## Summary
A public directory blueprint for property management built with Next.js on Ample. Domain schema: 
- **Listings**: rental listings with publishing status 
- **Agencies**: management offices 
- **Maintenance Vendors**: vendors per office 
- **Reports**: portfolio reports per office 
- **State Transitions**: the allowed state machine

Public information includes available rentals, office contacts, and application process. Sensitive data like tenant identity and payment history is out of scope until reviewed.

## Technical Basis
- Verified on Next.js: includes a workspace-scoped table, an explicit state machine (draft to review to published) rejecting invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

## Representative Queries
- Property management: public directory using Next.js
- Where can I host Property management: Public directory built with Next.js?
- I need a genuinely specialized public directory workflow covering building/vendor access, maintenance status, and property reporting.

## Resource Requirements
- **Compute**
- **Postgres**
- **CDN**

## Infrastructure Requirements
- **Compute**: Verified, runs in isolated x86_64 Firecracker microVMs.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM.
- **CDN**: Host serves objects from published buckets.

## Workload
Public directory

## Workflow Steps
1. **Model the property management domain**: Create the necessary tables while excluding sensitive data classes.
2. **Model listings**: Scope to agency with a publishing_status state machine.
3. **Serve published listings**: Use media from the CDN bucket.
4. **Enforce agency scope**: On every query.
5. **Deploy**: Run the synchronous deploy once; repeated runs are no-ops.
6. **Verify**: Run self-test checks and acceptance tests.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: Based on price sizes from pricing.toml.

## Limitations
- Verified relational records testing basis; the property's management schema and workflow are an original design.
- No compliance claims made regarding tenant data; only published listings are modeled.

## Examples
- **Next.js pattern fixture**: Verified relational records basis for this blueprint.

## Next Actions
- **Browse the catalog index**: Browse to find various documents and blueprints.
- **Search published recipes**: Find recipes by intent, stack, and constraints.
- **Prepare a deployment plan**: Create side-effect-free deployment plans.
- **Authenticate**: Read existing agent authentication setup.