# Membership associations: asset library using Laravel

## Summary
A asset library blueprint for membership associations built with Laravel on Ample. Domain schema:
- **course_groups** (chapter_or_program, start_at, end_at): chapters and programs as groups;
- **memberships** (course_group_id, member_email, tier, role, renewed_at): members and roles;
- **sessions** (course_group_id, starts_at, title, venue): meetings and events;
- **materials** (course_group_id, title, object_key, visibility): member resources;
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: about, chapters and benefits, public events, join information. Kept out of scope until handling is reviewed: member directory details, dues and payment records. Member directories are personal data; only public events and member-authorized resources are modeled.

Technical basis verified on Laravel: 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).

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

## Workflow Steps
1. **Model the membership associations domain**: Create the tables `course_groups`, `memberships`, `sessions`, `materials`, and `uploads`. Chapters and programs as groups live in `course_groups`; keep the sensitive classes (member directory details, dues, and payment records) 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.
7. **Verify**: Run the pattern self-test(s) from the example (`/p/browser-file-uploads`) and your own acceptance checks for the membership associations workflow.

### Examples
- **Laravel pattern fixture**: Verified browser file uploads basis for this blueprint.

## Limitations
- The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the membership associations 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. Member directories are personal data; only public events and member-authorized resources are modeled.
- 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.
- **Components**:
  - **app server**: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0.
  - **managed PostgreSQL database**: size `s-1vcpu-1gb`, quantity 1.0, 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 Membership associations schema and workflow build on that verified basis.
