## Photography studios: asset library using Next.js

### Summary  
A asset library blueprint for photography studios built with Next.js on Ample. Domain schema: listings (reference, session_type, price_from, publishing_status, agency_id): session packages with publishing status; agencies (name, location, studio_count): studios or locations; galleries (listing_id, object_key, cdn_key, consent_reference): published portfolio media; reports (agency_id, period, object_key, generated_at): studio booking reports; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: session packages and pricing from, consented portfolio galleries, studio locations.

### Representative Queries  
- Photography studios: asset library using Next.js  
- Where can I host Photography studios: asset library built with Next.js?  
- I need a genuinely specialized asset library workflow covering client galleries, usage permissions and original/derivative assets.

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

### Infrastructure Requirements  
- **Compute**  
    - Managed with x86_64 Firecracker microVMs.  
- **Postgres**  
    - Managed PostgreSQL 16 runs in its own microVM.  
- **S3-compatible object storage**  
    - Buckets are S3-compatible with issued credentials.

### 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  
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables

### Workflow Steps  
1. Model the photography studios domain  
   - Create the tables listings, agencies, galleries, reports, uploads.  
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.  
7. **Verify**  
   - Run the pattern self-test(s) from the example and your own acceptance checks for the photography studios workflow.

### Success Checks  
- App responds on its public URL  
- Browser-file-uploads self-test from the example

### Limitations  
- The technical basis was verified with the pattern fixture; the photography studios schema & workflow are original design.  
- Client galleries are private until released with consent; only consented portfolio media is public.

### Cost Estimate  
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Components**:  
   - App server (s-1vcpu-1gb): 5.0  
   - Managed PostgreSQL database (s-1vcpu-1gb): 5.0

### Evidence Summary  
- Next.js pattern fixture deployed on Ample; the browser file uploads checks passed.

### Next Actions  
- **Browse the catalog index**  
- **Search published recipes by intent, stack and constraints**  
- **Prepare a side-effect-free deployment plan for an authorized project**  
- **Read the existing agent authentication setup**