### Digital agencies: form collection using Laravel

A form collection blueprint for digital agencies built with Laravel on Ample. Domain schema:

- **client_entities** (name, brand, primary_contact_role): client brands
- **engagements** (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects
- **approval_rounds** (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds
- **deliverables** (engagement_id, title, object_key, version): final assets delivered
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: services and case studies, team, contact. Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials. Unreleased creative is confidential; brand platform credentials never belong in these flows.

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
- Digital agencies: form collection using Laravel
- Where can I host Digital agencies: Form collection built with Laravel?
- I need a genuinely specialized form collection workflow covering client projects, creative review and campaign deliverables.

#### Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

#### Infrastructure Requirements
1. **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.

2. **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.

3. **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.

#### Prerequisites
- 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 digital agencies data classes may be handled at all; this blueprint models public information only

#### Workflow Steps
1. **Model the digital agencies domain**: Create the tables client_entities, engagements, approval_rounds, deliverables, uploads. 
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.
   - **Command**: ample deploy . --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 digital agencies workflow.
   - **Command**: ample logs --kind build

#### Examples
- **Title**: Laravel pattern fixture
  - **Description**: Verified browser file uploads basis for this blueprint.
  - **Source Reference**: tests/deploy-canaries/laravel-patterns

#### Success Checks
1. **Description**: App responds on its public URL
   - **Kind**: http_get
   - **Path**: /
   - **Expect**: ample canary laravel patterns
2. **Description**: 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 digital agencies 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. Unreleased creative is confidential; brand platform credentials never belong in these flows.
- 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.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - App server (s-1vcpu-1gb): $5.0 per month
  - Managed PostgreSQL database (s-1vcpu-1gb): $5.0 per month
- **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.

#### Next Actions
- **Browse the catalog index**: API endpoint `/v1/catalog`
- **Search published recipes by intent, stack and constraints**: POST to `/v1/catalog/search`
- **Prepare a side-effect-free deployment plan for an authorized project**: POST to `/v1/catalog/plan`
- **Read the existing agent authentication setup**: GET from `/mcp/setup`
- **Browse Digital agencies**: API endpoint `/v1/catalog/nodes/industry%3Adigital-agencies`
- **Browse Form collection**: API endpoint `/v1/catalog/nodes/workload%3Aform-collection`
- **Browse Laravel**: API endpoint `/v1/catalog/nodes/stack%3Aframework-laravel`
- **Browse Deploy web app**: API endpoint `/v1/catalog/nodes/intent%3Adeploy-web-app`.
