# Law firms: project tracker using Django

A project tracker blueprint for law firms built with Django on Ample. Domain schema: 
- **client_entities** (name, entity_type, conflict_check_reference): clients with conflict-check status;  
- **matters** (client_entity_id, practice_area, opened_at, closed_at, status): engagement periods as matters;  
- **document_requests** (matter_id, title, due_at, status, uploaded_object_key): documents requested from the client;  
- **shared_documents** (matter_id, title, object_key, authorized_role): documents released to authorized client contacts;  
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

Public information: practice areas and attorney profiles, intake process and fee structure overview, office locations. Kept out of scope until handling is reviewed: privileged communications and case files, identity and financial documents, opposing-party information. Matter documents are privileged; the portal models per-matter authorization. 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 law firms data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

install
```bash
python3 -m pip install --target .ample/python -r requirements.txt
```
runtime
```bash
python
```
sizes
```bash
1vcpu-1gb
```
start
```bash
PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
```
template
```bash
python-3.12
```

## Steps

1. **Model the law firms domain.** Create the tables client_entities, matters, document_requests, shared_documents, state_transitions. Clients with conflict-check status lives in client_entities; keep the sensitive classes (privileged communications and case files, identity and financial documents, opposing-party information) 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.

```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. **Verify.** Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the law firms workflow.

```bash
    $ 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 Law firms 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 law firms schema and workflow are an original design for this blueprint, built on that basis.
- Matter documents are privileged; the portal models per-matter authorization.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
