Law firms: project tracker using Laravel · Ample Computer

Law firms: project tracker using Laravel

A project tracker blueprint for law firms built with Laravel on Ample. Domain schema:

What it runs on

You need

Exact tested configuration

Steps

  1. Model the law firms domain. Create the tables client_entities, matters, document_requests, shared_documents, state_transitions. Clients with conflict-check status live 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=...
    
  7. 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

Evidence

  1. November 6, 2026 · canary run

    Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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 build on that verified basis.

Tested examples

What it doesn’t cover