## Tutoring centers: event registration using Django

### Summary
A event registration blueprint for tutoring centers built with Django on Ample. Domain schema:
- **course_groups** (subject, level, start_at, end_at, capacity): tutoring groups;
- **memberships** (course_group_id, student_reference, guardian_reference, role): students, guardians and tutors;
- **sessions** (course_group_id, starts_at, tutor, attendance_count): session events;
- **materials** (course_group_id, title, object_key, visibility): worksheets and answer keys;
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

Public information: subjects and levels, schedule and locations, tutor qualifications. Kept out of scope until handling is reviewed: minor students and guardian identity, progress reports. Data about minors is sensitive; only group schedules and materials are modeled here.

### Representative Queries
- Tutoring centers: event registration using Django
- Where can I host Tutoring centers: Event registration built with Django?
- I need a genuinely specialized event registration workflow covering course-group membership, session events and teaching materials.

### 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 Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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 tutoring centers data classes may be handled at all; this blueprint models public information only

### Workflow Steps
1. **Model the tutoring centers domain**: Create the tables course_groups, memberships, sessions, materials, events. Tutoring groups lives in course_groups; keep the sensitive classes (minor students and guardian identity, progress reports) 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.
7. **Verify**: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the tutoring centers workflow.

### Limitations
- The technical basis (transactional workflows on Django) was verified with the pattern fixture; the tutoring centers 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. Data about minors is sensitive; only group schedules and materials are modeled here.
- Verified on the python-3.12 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.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision.
- **Components**:
  - app server (s-1vcpu-1gb): 5.0
  - managed PostgreSQL database (s-1vcpu-1gb): 5.0

### Success Checks
- app responds on its public URL
- transactional-workflows self-test from the example

### Next Actions  
- **Browse the catalog index**  
- **Search published recipes by intent, stack and constraints**  
- **Prepare a side-effect-free deployment plan for an authorized project**  
- **Read the existing agent authentication setup**  
- **Browse Tutoring centers**  
- **Browse Event registration**  
- **Browse Django**  
- **Browse Deploy web app**