## Membership associations: event registration using Laravel

### Summary
A event registration 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; 
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

### Representative Queries
- Membership associations: event registration using Laravel
- Where can I host Membership associations: Event registration built with Laravel?
- I need a genuinely specialized event registration workflow covering membership tiers, event eligibility and shared resources.

### 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 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 membership associations data classes may be handled at all; this blueprint models public information only

### Workflow Steps
1. **Model the membership associations domain**: Create the tables course_groups, memberships, sessions, materials, events. Chapters and programs as groups lives in course_groups; keep the sensitive classes (member directory details, dues and payment records) out of this schema.
2. **Workflow step 1**: Model sessions with capacity and registrations with status
3. **Workflow step 2**: Register transactionally with a capacity check and an event per registration
4. **Workflow step 3**: Reject stale concurrent updates
5. **Workflow step 4**: Deploy and verify history and conflict handling
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
    - Command: 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/transactional-workflows) and your own acceptance checks for the membership associations workflow.
    - Command: ample logs  --kind build

### Limitations
- The technical basis (transactional workflows 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.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.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.

- **Components**:
  - App server: size s-1vcpu-1gb
  - Managed PostgreSQL database: size s-1vcpu-1gb

### Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary laravel patterns
2. **Transactional workflows self-test from the example**  
   - Kind: http_get  
   - Path: /p/transactional-workflows  
   - Expect: see the pattern fixture checks

### Evidence Summary
- **Type**: canary_run  
- **Summary**: Laravel pattern fixture deployed on Ample; the transactional workflows checks passed.
- **Observed At**: 2026-09-20T20:36:21Z  
- **Last Verified At**: 2026-09-20T20:36:21Z

### Formats
- [HTML](/content/blueprints/membership-associations/event-registration/laravel/index.html)
- [Markdown](/content/blueprints/membership-associations/event-registration/laravel.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Amembership-associations%3Aevent-registration%3Alaravel)
