## The short version

A public directory blueprint for property management built with Django 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;  
**state_transitions** (record_type, from_state, to_state): the allowed state machine.  
Public information: available rentals, office contacts, application process.  
Kept out of scope until handling is reviewed: tenant identity and payment history, inspection reports with personal data.  
Tenant data is personal and often regulated; only published listings and office-scoped reporting are modeled.  
Technical basis verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)  
- [Postgres](/content/discover/primitive/postgres/index.html): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)  
- [CDN](/content/discover/primitive/cdn/index.html): verified (A published bucket's objects are served at its public_url. It does not front app compute and is not a cache or key-value store.)

## Before you start

- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)  
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)  
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)  
- A review of which property management data classes may be handled at all; this blueprint models public information only

## How to do it

1.  **Model the property management domain**  
   Create the tables listings, agencies, maintenance_vendors, reports, state_transitions. Rental listings with publishing status lives 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 listings with a publishing_status state machine scoped to the agency  
3.  **Workflow step 2**  
   Serve only published listings, with media from the CDN bucket  
4.  **Workflow step 3**  
   Enforce the agency scope on every query  
5.  **Workflow step 4**  
   Deploy and verify a published listing and that unpublished listings are absent  
6.  **Deploy**  
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```  
   ample deploy . --name <app-name> --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...  
   ```  
7.  **Verify**  
   Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the property management workflow.

```  
   ample logs <deployment_id> --kind build  
   ```

## Tested examples

- **Django pattern fixture** (`tests/deploy-canaries/django-patterns`): Verified relational records basis for this blueprint.

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary django patterns)  
- relational-records self-test from the example (`/p/relational-records` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD  
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD  
Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-20T03:31:44Z at revision `03b6402b1b3e19178985f08ea4033804521d85d4 (CLI b75e104)`: Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); the relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Property management schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T03:31:44Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.

## Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)  
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)  
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)  
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)  
- Browse Property management (`GET /v1/catalog/nodes/industry%3Aproperty-management` on the api origin; authentication not required, approval not required)  
- Browse Public directory (`GET /v1/catalog/nodes/workload%3Apublic-directory` on the api origin; authentication not required, approval not required)  
- Browse Django (`GET /v1/catalog/nodes/stack%3Aframework-django` on the api origin; authentication not required, approval not required)  
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required)  
Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status

Recipe `page:blueprints:property-management:public-directory:django`. Revision r1.  
release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**  
Formats: [HTML](/content/blueprints/property-management/public-directory/django/index.html) | [Markdown](/content/blueprints/property-management/public-directory/django.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aproperty-management%3Apublic-directory%3Adjango)