# Professional training: event registration using Next.js

## Summary
A event registration blueprint for professional training built with Next.js on Ample. Domain schema: 
- **course_groups** (certification, cohort, start_at, end_at): certification cohorts;  
- **memberships** (course_group_id, participant_email, employer, role): participants and trainers;  
- **sessions** (course_group_id, starts_at, module, location_or_link): training sessions;  
- **materials** (course_group_id, module, object_key, visibility): course materials and exam guides;  
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.  
Public information: certification catalog, cohort dates, trainer credentials. Kept out of scope until handling is reviewed: exam results, employer billing, participant identity. Exam results and certifications are personal records; only cohort logistics and materials 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
- Professional training: event registration using Next.js  
- Where can I host Professional training: Event registration built with Next.js?  
- I need a genuinely specialized event registration workflow covering course cohorts, enrollment events and learning-resource access.

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

## Workflow Steps
1. **Model the professional training domain**: Create the tables course_groups, memberships, sessions, materials, events. Certification cohorts lives in course_groups; keep the sensitive classes (exam results, employer billing, participant identity) 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 professional training workflow.
   Command: `ample logs  --kind build`

## Examples
- **Next.js pattern fixture**: Verified transactional workflows basis for this blueprint.
  - Source Ref: tests/deploy-canaries/next-js-patterns

## 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
- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the professional training 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. Exam results and certifications are personal records; only cohort logistics and materials are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the node-22 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  
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, monthlyAmount: 5.0  
  - Managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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
- **Canary Run**: 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 Professional training 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

## Last Verified At
2026-09-21T02:34:39Z

## Formats
- [HTML Format](/content/blueprints/professional-training/event-registration/next-js/index.html)  
- [Markdown Format](/content/blueprints/professional-training/event-registration/next-js.md)  
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aprofessional-training%3Aevent-registration%3Anext-js)

## Next Actions
1. **Browse the catalog index**:  
   Method: GET  
   Relative Path: /v1/catalog  
   Requires Authentication: false  
   Requires Approval: false
2. **Search published recipes by intent, stack and constraints**:  
   Method: POST  
   Relative Path: /v1/catalog/search  
   Requires Authentication: false  
   Requires Approval: false  
   Parameters: {"body":{"limit":5,"query":"Professional training: event registration using Next.js"}} 
3. **Prepare a side-effect-free deployment plan for an authorized project**:  
   Method: POST  
   Relative Path: /v1/catalog/plan  
   Requires Authentication: true  
   Requires Approval: false  
   Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:blueprints:professional-training:event-registration:next-js","recipeRevision":"r1"}} 
4. **Read the existing agent authentication setup**:  
   Method: GET  
   Relative Path: /mcp/setup  
   Requires Authentication: false  
   Requires Approval: false  
5. **Browse Professional training**:  
   Method: GET  
   Relative Path: /v1/catalog/nodes/industry%3Aprofessional-training  
   Requires Authentication: false  
   Requires Approval: false  
6. **Browse Event registration**:  
   Method: GET  
   Relative Path: /v1/catalog/nodes/workload%3Aevent-registration  
   Requires Authentication: false  
   Requires Approval: false  
7. **Browse Next.js**:  
   Method: GET  
   Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js  
   Requires Authentication: false  
   Requires Approval: false  
8. **Browse Deploy web app**:  
   Method: GET  
   Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app  
   Requires Authentication: false  
   Requires Approval: false
