# Digital agencies: client portal using Laravel

## Summary
A client portal 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;
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
1. **Compute**: 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**: 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**: 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, document_access. Client brands lives in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) out of this schema.
2. **Workflow step 1:** Model client entities and engagement periods; every document belongs to one engagement.
3. **Workflow step 2:** Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
4. **Workflow step 3:** Store documents in the private bucket and stream them through the app.
5. **Workflow step 4:** Deploy and verify the negative authorization tests and an authorized download.
6. **Deploy:** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify:** Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the digital agencies workflow.

## Success Checks
1. App responds on its public URL.
2. Private-document-library self-test from the example.

## Limitations
- The technical basis (private document library on Laravel) was verified with the pattern fixture.
- No health, financial, privacy or other compliance claim is made.
- 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, 1.0, $5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, 1.0, $5.0

## Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse Digital agencies**
6. **Browse Client portal**
7. **Browse Laravel**
8. **Browse Deploy web app**
