## Video production: asset library using Next.js

A asset library blueprint for video production built with Next.js 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;  
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

### 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 Next.js:
- 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
- Video production: asset library using Next.js  
- Where can I host Video production: Asset library built with Next.js?  
- I need a genuinely specialized asset library workflow covering project reviewers, delivery specifications and video asset versions.

### 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 Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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.

### Tested Configuration
- **Template**: node-22  
- **Runtime**: node  
- **Size**: s-1vcpu-1gb  
- **Install**: npm install  
- **Build**: npm run build --if-present  
- **Start**: npm run start

### Workflow Steps
1. Model the video production domain: Create the tables customer_workspaces, projects, cuts, customer_assets, uploads.  
   Client organizations live in customer_workspaces; keep the sensitive classes out of this schema.
2. Workflow step 1: Model assets linked to their owning group or workspace.
3. Workflow step 2: Validate uploads and store them in the private bucket; link each object to its row.
4. Workflow step 3: Authorize downloads by membership.
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.
   ```bash
   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 video production workflow.
   ```bash
   ample logs  --kind build
   ```

### Success Checks
- App responds on its public URL (expect: ample canary next js patterns).
- Browser-file-uploads self-test from the example (expect: see the pattern fixture checks).

### Limitations
- The technical basis (browser file uploads on Next.js) 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; the storage checks here use small objects, so verify large-file behavior separately.  
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

### 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, quantity: 1.0, monthlyAmount: 5.0  
   - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
- 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
- Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the browser file uploads checks passed.
- Checks include 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.

### Next Actions
1. **Browse the catalog index**: GET /v1/catalog.  
2. **Search published recipes**: POST /v1/catalog/search (body: {"limit": 5, "query": "Video production: asset library using Next.js"}).  
3. **Prepare a deployment plan**: POST /v1/catalog/plan (body: {"inputs": {}, "projectId": "", "recipeId": "page:blueprints:video-production:asset-library:next-js", "recipeRevision": "r1"}).  
4. **Read the existing agent authentication setup**: GET /mcp/setup.
5. **Browse Video production**: GET /v1/catalog/nodes/industry%3Avideo-production.
6. **Browse Asset library**: GET /v1/catalog/nodes/workload%3Aasset-library.
7. **Browse Next.js**: GET /v1/catalog/nodes/stack%3Aframework-next-js.
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app.