# Bookkeeping practices: project tracker using Django

A project tracker blueprint for bookkeeping practices built with Django on Ample. Domain schema: client_entities (legal_name, entity_type, accounting_software, period_cadence): clients and their bookkeeping cadence; engagements (client_entity_id, period_start, period_end, close_status): monthly or quarterly close engagements; document_requests (engagement_id, category, due_at, status, uploaded_object_key): receipts, statements and payroll summaries requested; close_checklists (engagement_id, item, done_at): close tasks per period; state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: service packages and cadence, onboarding checklist, contact details. Kept out of scope until handling is reviewed: bank statements and receipts, payroll data, login credentials for accounting software. Never store client accounting-software credentials in these flows; financial records are sensitive. 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 runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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 bookkeeping practices data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt  
runtimepython  
sizes-1vcpu-1gb  
startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py  
templatepython-3.12

## Steps

1. **Model the bookkeeping practices domain.** Create the tables client_entities, engagements, document_requests, close_checklists, state_transitions. Clients and their bookkeeping cadence lives in client_entities; keep the sensitive classes (bank statements and receipts, payroll data, login credentials for accounting software) out of this schema.

2. **Workflow step 1.** Model engagements and workstreams with explicit status transitions

3. **Workflow step 2.** Scope every query by client entity

4. **Workflow step 3.** Attach deliverables as private objects linked to workstreams

5. **Workflow step 4.** Deploy and verify transitions and cross-client isolation

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

7. **Verify.** Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the bookkeeping practices workflow.

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

## How it was checked

✓app responds on its public URL· http get/ → “ample canary django patterns”  
✓relational-records self-test from the example· http get/p/relational-records → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
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 Bookkeeping practices schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified relational records basis for this blueprint.

## What it doesn’t cover

- The technical basis (relational records on Django) was verified with the pattern fixture; the bookkeeping practices schema and workflow are an original design for this blueprint, built on that basis.

- Never store client accounting-software credentials in these flows; financial records are sensitive.
