### Membership associations: event registration using Next.js

A event registration blueprint for membership associations built with Next.js 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 Next.js: 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 Next.js
- Where can I host Membership associations: Event registration built with Next.js?
- 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**  
   - Status: verified  
   - Summary: 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**  
   - Status: verified  
   - Summary: 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**  
   - Status: verified  
   - Summary: 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 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 live 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`

### Success Checks
- **app responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary next js patterns

- **transactional-workflows self-test from the example**  
   - Kind: http_get  
   - Path: /p/transactional-workflows  
   - Expect: see the pattern fixture checks

### Limitations
1. The technical basis (transactional workflows on Next.js) 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.
2. No health, financial, privacy or other compliance claim is made. Member directories are personal data; only public events and member-authorized resources are modeled.
3. Public content and synthetic examples only until actual data-handling requirements have been reviewed.
4. Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
5. Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
6. 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  
- Authoritative: true  
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- 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
- 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
- **Kind**: canary_run  
  **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 transactional workflows checks passed: 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). The blueprint's Membership associations schema and workflow below build on that verified basis and were not separately executed.
  **Observed At**: 2026-09-21T02:34:39Z  
  **Implementation Revision**: 1d28ae0-dirty (CLI 0.1.21)  
  **Expires At**: 2027-03-20T02:34:39Z  
  **Scope**:  
   - Checks: [/p/transactional-workflows]  
   - Pattern: pattern:transactional-workflows  
   - Template: node-22

### Next Actions
- **Browse the catalog index**  
   - Operation ID: catalog_index  
   - Method: GET  
   - Relative Path: /v1/catalog  
   - Requires Authentication: false
- **Search published recipes by intent, stack and constraints**  
   - Operation ID: search_recipes  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters: {"body":{"limit":5,"query":"Membership associations: event registration using Next.js"}}  
   - Requires Authentication: false  
- **Prepare a side-effect-free deployment plan for an authorized project**  
   - Operation ID: plan_deployment  
   - Method: POST  
   - Relative Path: /v1/catalog/plan  
   - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:blueprints:membership-associations:event-registration:next-js","recipeRevision":"r1"}}  
   - Requires Authentication: true  
- **Read the existing agent authentication setup**  
   - Operation ID: existing_auth_setup  
   - Method: GET  
   - Relative Path: /mcp/setup  
   - Requires Authentication: false  
- **Browse Membership associations**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/industry%3Amembership-associations  
   - Parameters: {"nodeId":"industry:membership-associations"}  
   - Requires Authentication: false  
- **Browse Event registration**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Aevent-registration  
   - Parameters: {"nodeId":"workload:event-registration"}  
   - Requires Authentication: false  
- **Browse Next.js**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js  
   - Parameters: {"nodeId":"stack:framework-next-js"}  
   - Requires Authentication: false  
- **Browse Deploy web app**  
   - Operation ID: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app  
   - Parameters: {"nodeId":"intent:deploy-web-app"}  
   - Requires Authentication: false