### Digital agencies: form collection using Django

#### Summary
A form collection blueprint for digital agencies built with Django on Ample. Domain schema: 
- **client_entities** (name, brand, primary_contact_role): client brands;
- **engagements** (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects;
- **approval_rounds** (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds;
- **deliverables** (engagement_id, title, object_key, version): final assets delivered;
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: services and case studies, team, contact. 
Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials. 
Unreleased creative is confidential; brand platform credentials never belong in these flows. 
Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

#### Representative Queries
- Digital agencies: form collection using Django
- Where can I host Digital agencies: Form collection built with Django?
- I need a genuinely specialized form collection workflow covering client projects, creative review and campaign deliverables.

#### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

#### 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.
- **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 digital agencies domain**: Create the tables client_entities, engagements, approval_rounds, deliverables, uploads. Client brands lives in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) out of this schema.
2. **Workflow step 1**: Model document requests per engagement with due dates and status.
3. **Workflow step 2**: Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request.
4. **Workflow step 3**: Authorize uploads by client entity.
5. **Workflow step 4**: Deploy and verify rejection of disallowed files and a linked upload.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   - Command: `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=...`
7. **Verify**: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the digital agencies workflow.
   - Command: `ample logs --kind build`

### Limitations
- The technical basis (browser file uploads on Django) was verified with the pattern fixture; the digital agencies 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. Unreleased creative is confidential; brand platform credentials never belong in these flows.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.