# Course creators: asset library using Django

## Summary
A asset library blueprint for course creators built with Django on Ample. Domain schema:
- **course_groups** (name, start_at, end_at, capacity): cohorts as course groups;
- **memberships** (course_group_id, member_email, role, joined_at): learner and instructor membership;
- **sessions** (course_group_id, starts_at, title, recording_object_key): session events and recordings;
- **materials** (course_group_id, title, object_key, visibility): teaching materials;
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: course catalog and syllabus, instructor profile, schedule. Kept out of scope until handling is reviewed: learner progress and grades, recordings showing learners, payment status. Recordings and progress data are personal data; materials are authorized per course group. Technical basis verified on Django: 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).

## Framework
- **Django**

## Workload
- **Asset library**

## Industry
- **Course creators**

## 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.

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

## Workflow Steps
1. **Model the course creators domain**: Create the tables course_groups, memberships, sessions, materials, uploads. Cohorts as course groups live in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) 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 course creators workflow.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - **App server**: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  - **Managed PostgreSQL database**: 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.

## Limitations
- The technical basis (browser file uploads on Django) was verified with the pattern fixture; the course creators 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. Recordings and progress data are personal data; materials are authorized per course group.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes by intent, stack and constraints**: POST /v1/catalog/search  
- **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan
- **Read the existing agent authentication setup**: GET /mcp/setup
- **Browse Course creators**: GET /v1/catalog/nodes/industry%3Acourse-creators
- **Browse Asset library**: GET /v1/catalog/nodes/workload%3Aasset-library
- **Browse Django**: GET /v1/catalog/nodes/stack%3Aframework-django
- **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app