# Law firms: form collection using Laravel

A form collection blueprint for law firms built with Laravel 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;  
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

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 Laravel: 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 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 Laravel project (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)

- 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  
  composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

- runtime  
  php

- sizes-1vcpu-1gb

- start  
  frankenphp php-server --listen :$PORT --root public

- template  
  php-8.5

## Steps

1. **Model the law firms domain.** Create the tables client_entities, matters, document_requests, shared_documents, uploads. 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 document requests per engagement with due dates and status

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

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

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

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/browser-file-uploads) 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 laravel patterns”  
✓ browser-file-uploads self-test from the example· http get/p/browser-file-uploads → “see the pattern fixture checks”

## Evidence

- 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 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 Law firms schema and workflow build on that verified basis.

## Tested examples

- **Laravel pattern fixture.** Verified browser file uploads basis for this blueprint.

## What it doesn’t cover

- The technical basis (browser file uploads on Laravel) 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 php-8.5 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.
