### Photography studios: documentation site using Django

A documentation site blueprint for photography studios built with Django on Ample.  
**Domain schema:**  
- **listings** (reference, session_type, price_from, publishing_status, agency_id): session packages with publishing status;  
- **agencies** (name, location, studio_count): studios or locations;  
- **galleries** (listing_id, object_key, cdn_key, consent_reference): published portfolio media;  
- **reports** (agency_id, period, object_key, generated_at): studio booking reports;  
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

Public information includes: session packages and pricing from, consented portfolio galleries, studio locations.  
Kept out of scope until handling is reviewed: client galleries before release, minors in photographs, payment details. Client galleries are private until released with consent; only consented portfolio media is public.

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

**Representative Queries:**  
- Photography studios: documentation site using Django  
- Where can I host Photography studios: Documentation site built with Django?  
- I need a genuinely specialized documentation site workflow covering client galleries, usage permissions and original/derivative assets.

**Resource Requirements:**  
- primitive:compute  
- primitive:postgres  
- primitive:cdn

**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.  
- **CDN**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

### Workflow Steps
1. **Model the photography studios domain**  
   Create the tables listings, agencies, galleries, reports, state_transitions. Session packages with publishing status lives in listings; keep the sensitive classes (client galleries before release, minors in photographs, payment details) out of this schema.  
2. **Workflow step 1**  
   Model versioned documents with a state machine (draft, review, published) scoped to a product version  
3. **Workflow step 2**  
   Publish assets for released versions to the CDN bucket  
4. **Workflow step 3**  
   Serve only published versions publicly  
5. **Workflow step 4**  
   Deploy and verify the version list and a published page  
6. **Deploy**  
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
   ```bash  
   ample deploy . --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 photography studios workflow.  
   ```bash  
   ample logs  --kind build  
   ```

### Limitations
- The technical basis (relational records on Django) was verified with the pattern fixture; the photography studios 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. Client galleries are private until released with consent; only consented portfolio media is public.  
- Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

### 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: $5.00/month  
    - managed PostgreSQL database: s-1vcpu-1gb: $5.00/month  
- **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.