Law firms: project tracker using Next.js · Ample Computer

Law firms: project tracker using Next.js

A project tracker blueprint for law firms built with Next.js 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 Next.js: 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).

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present
install npm install
runtime node
sizes-1vcpu-1gb
start npm run start
template node-22

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.

$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  1. Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the law firms workflow.
$ ample logs <deployment_id> --kind build

How it was checked

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

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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

What it doesn’t cover