# Video Production: Client Portal Using Laravel

## Summary
A client portal blueprint for video production built with Laravel on Ample. Domain schema:
- **customer_workspaces** (client_name, project_count): client organizations;
- **projects** (workspace_id, title, stage, delivery_due_at): productions in flight;
- **cuts** (project_id, version, object_key, review_status, reviewed_at): versioned cuts for review;
- **customer_assets** (workspace_id, project_id, object_key, visibility): final deliverables and raw footage access;
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information: showreel and services, production process, contact. Kept out of scope until handling is reviewed: unreleased footage, talent releases and contracts, client brand material. Footage is large and confidential; the storage checks here use small objects, so verify large-file behavior separately. 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).

## Representative Queries
- Video production: client portal using Laravel
- Where can I host Video production: Client portal built with Laravel?
- I need a genuinely specialized client portal workflow covering project reviewers, delivery specifications and video asset versions.

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

## Infrastructure Requirements
- **Compute:** Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.
- **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 video production data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the video production domain**: Create the tables customer_workspaces, projects, cuts, customer_assets, document_access.
2. **Model client entities and engagement periods**: every document belongs to one engagement.
3. **Authorize by client entity and role before any storage access**: (401 without identity, 403 for the wrong client).
4. **Store documents in the private bucket and stream them through the app**.
5. **Deploy and verify** the negative authorization tests and an authorized download.
6. **Run the synchronous deploy once** and read the result.

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

## Limitations
- The technical basis (private document library on Laravel) was verified with the pattern fixture; the video production 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. Footage is large and confidential; verify large-file behavior separately.

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** $10.00 
- **Basis:** Apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Known Issues
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.
