page:blueprints:law firms:form collection:laravel
Law firms: Form collection using Laravel
Summary
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 includes 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 only. Professional-conduct and confidentiality obligations are not established here. 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).
Representative Queries
- Law firms: form collection using Laravel
- Where can I host Law firms: Form collection built with Laravel?
- I need a genuinely specialized form collection workflow covering matter-based access separation and confidential document handling.
Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
Infrastructure Requirements
- Compute
- Status: verified
- Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- Postgres
- Status: verified
- Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- S3-compatible object storage
- Status: verified
- Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
Workflow Steps
- Model the law firms domain
- Create the tables client_entities, matters, document_requests, shared_documents, uploads. 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.
- Workflow step 1
- Model document requests per engagement with due dates and status
- Workflow step 2
- Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request
- Workflow step 3
- Authorize uploads by client entity
- Workflow step 4
- Deploy and verify rejection of disallowed files and a linked upload
- Deploy
- Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
- Command:
ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
- Verify
- Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the law firms workflow.
- Command:
ample logs --kind build
Examples
- Laravel pattern fixture
- Verified browser file uploads basis for this blueprint.
- Source Reference:
tests/deploy-canaries/laravel-patterns
Success Checks
- Application responds on its public URL
- Kind: http_get
- Path: /
- Expect: ample canary laravel patterns
- Browser-file-uploads self-test from the example
- Kind: http_get
- Path: /p/browser-file-uploads
- Expect: see the pattern fixture checks
Limitations
- 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 and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Matter documents are privileged; the portal models per-matter authorization only. Professional-conduct and confidentiality obligations are not established here.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.
Cost Estimate
- Currency: USD
- Monthly Amount: $10.00
- Authoritative: true
- Basis: size prices from pricing.toml (loaded by the API) at build revision
1ac5595375130d45290090e82ed0f554ccd45405-dirty - Components:
- App server
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: $5.00
- Managed PostgreSQL database
- Size: s-1vcpu-1gb
- Quantity: 1.0
- Monthly Amount: $5.00
- App server
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
Evidence Summary
- Kind: canary_run
- Summary: 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 below build on that verified basis and were not separately executed.
- Observed At: 2026-09-20T20:36:21Z
- Implementation Revision:
118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c) - Expires At: 2027-03-19T20:36:21Z
- Scope:
- Checks:
/p/browser-file-uploads - Pattern:
pattern:browser-file-uploads - Template:
php-8.5
- Checks:
Last Verified At
2026-09-20T20:36:21Z
Next Actions
- Browse the catalog index
- Action ID:
browse-catalog - Operation ID:
catalog_index - Method: GET
- Relative Path:
/v1/catalog - Requires Authentication: false
- Requires Approval: false
- Action ID:
- Search published recipes by intent, stack and constraints
- Action ID:
search-recipes - Operation ID:
search_recipes - Method: POST
- Relative Path:
/v1/catalog/search - Parameters:
- Body:
- Limit: 5
- Query:
Law firms: form collection using Laravel
- Body:
- Requires Authentication: false
- Requires Approval: false
- Action ID:
- Prepare a side-effect-free deployment plan for an authorized project
- Action ID:
plan:page:blueprints:law-firms:form-collection:laravel - Operation ID:
plan_deployment - Method: POST
- Relative Path:
/v1/catalog/plan - Parameters:
- Body:
- Inputs: {}
- Project ID: ""
- Recipe ID:
page:blueprints:law-firms:form-collection:laravel - Recipe Revision:
r1
- Body:
- Requires Authentication: true
- Requires Approval: false
- Action ID:
- Read the existing agent authentication setup
- Action ID:
auth-setup - Operation ID:
existing_auth_setup - Method: GET
- Relative Path:
/mcp/setup - Requires Authentication: false
- Requires Approval: false
- Action ID:
- Browse Law firms
- Action ID:
browse:industry:law-firms - Operation ID:
browse_node - Method: GET
- Relative Path:
/v1/catalog/nodes/industry%3Alaw-firms - Parameters:
- Node ID:
industry:law-firms
- Node ID:
- Requires Authentication: false
- Requires Approval: false
- Action ID:
- Browse Form collection
- Action ID:
browse:workload:form-collection - Operation ID:
browse_node - Method: GET
- Relative Path:
/v1/catalog/nodes/workload%3Aform-collection - Parameters:
- Node ID:
workload:form-collection
- Node ID:
- Requires Authentication: false
- Requires Approval: false
- Action ID:
- Browse Laravel
- Action ID:
browse:stack:framework-laravel - Operation ID:
browse_node - Method: GET
- Relative Path:
/v1/catalog/nodes/stack%3Aframework-laravel - Parameters:
- Node ID:
stack:framework-laravel
- Node ID:
- Requires Authentication: false
- Requires Approval: false
- Action ID:
- Browse Deploy web app
- Action ID:
browse:intent:deploy-web-app - Operation ID:
browse_node - Method: GET
- Relative Path:
/v1/catalog/nodes/intent%3Adeploy-web-app - Parameters:
- Node ID:
intent:deploy-web-app
- Node ID:
- Requires Authentication: false
- Requires Approval: false
- Action ID: