## Creator businesses: asset library using Laravel

### Summary
A asset library blueprint for creator businesses built with Laravel on Ample. Domain schema:
- **customer_workspaces** (name, membership_tier, joined_at): member accounts or communities;
- **content_items** (title, tier_required, object_key, published_at, version): versioned content releases;
- **customer_assets** (workspace_id, title, object_key, visibility): downloads granted to a member;
- **releases** (content_item_id, version, notes): release notes per version;
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: free content and previews, membership tiers, creator profile. Kept out of scope until handling is reviewed: member identity and payment status, private community posts. Member payment status comes from your payment provider; it is not modeled here and no PCI claim is made.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive: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
1. 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)
2. A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
3. Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
4. A review of which creator businesses data classes may be handled at all; this blueprint models public information only

### Workflow Steps
1. **Model the creator businesses domain**: Create the tables customer_workspaces, content_items, customer_assets, releases, uploads. Member accounts or communities live in customer_workspaces; keep the sensitive classes out of this schema.
2. **Model assets linked to their owning group or workspace**
3. **Validate uploads and store them in the private bucket**; link each object to its row
4. **Authorize downloads by membership**
5. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
6. **Verify**: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the creator businesses 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 creator businesses 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. 
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

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

### Evidence Summary
- **Canary run**: Laravel pattern fixture deployed on Ample; the browser file uploads checks passed: content-type and size validation. The blueprint's Creator businesses schema and workflow below build on that verified basis.
