## The short version

A form collection blueprint for accounting firms built with Django on Ample. Domain schema: client_entities (legal_name, entity_type, fiscal_year_end, jurisdiction): the businesses and individuals served; engagements (client_entity_id, service_line, period_start, period_end, status): bookkeeping, tax and audit engagements by period; document_requests (engagement_id, title, due_at, status, uploaded_object_key): requests for source documents; deliverables (engagement_id, title, object_key, released_at): returns and statements released to the client; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: service lines and typical engagement periods, filing calendars and deadlines, office locations. Kept out of scope until handling is reviewed: tax identifiers and financial statements, bank and payroll records, identity documents. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance. 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).

## 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.)
- [S3-compatible object storage](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## 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
- A review of which accounting firms data classes may be handled at all; this blueprint models public information only

## How to do it

1. 1  
### Model the accounting firms domain
   Create the tables client_entities, engagements, document_requests, deliverables, uploads. The businesses and individuals served lives in client_entities; keep the sensitive classes (tax identifiers and financial statements, bank and payroll records, identity documents) out of this schema.

2. 2  
### Workflow step 1
   Model document requests per engagement with due dates and status

3. 3  
### Workflow step 2
   Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request

4. 4  
### Workflow step 3
   Authorize uploads by client entity

5. 5  
### Workflow step 4
   Deploy and verify rejection of disallowed files and a linked upload

6. 6  
### Deploy
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```bash
   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=...
   ```

7. 7  
### Verify
   Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the accounting firms workflow.

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

## Tested examples

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

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary django patterns)
- browser-file-uploads self-test from the example (`/p/browser-file-uploads` 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 browser file uploads checks passed: 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). The blueprint's Accounting firms 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 Accounting firms (`GET /v1/catalog/nodes/industry%3Aaccounting-firms` on the api origin; authentication not required, approval not required)
- Browse Form collection (`GET /v1/catalog/nodes/workload%3Aform-collection` 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:accounting-firms:form-collection:django`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**  
Formats: [HTML](/content/blueprints/accounting-firms/form-collection/django/index.html) | [Markdown](/content/blueprints/accounting-firms/form-collection/django.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aaccounting-firms%3Aform-collection%3Adjango)