# Junior producer curriculum

Designed for self-paced, offline-friendly study.

Start with Module 1 and keep each output for the [fictional capstone](exercises/fictional-capstone.md). Use the linked guides as references. Check the finished package with the [assessment rubric](ASSESSMENT-RUBRIC.md); do not treat a completed worksheet as permission to release real material.

| Module | Learn | Produce | Gate |
| --- | --- | --- | --- |
| [1. Define](docs/INDEPENDENT-CREATOR-GUIDE.md#2-build-the-minimum-professional-package) | Roles, scope, audience, evidence classes | One-page project charter | Function is clear; proposals are labeled |
| [2. Design](docs/creative-brief.md) | Music-first story structure and creative briefs | Track/episode map and brief | No third-party material treated as cleared |
| [3. Organize](templates/contribution-record.md) | Credits, files, versions, metadata, backups | Folder map, naming rules, contribution log | Private evidence stays private |
| [4. Budget](docs/financial-waterfall-and-cash-timing.md) | Costs, milestones, cash timing, recoupment | Budget plus three planning cases; use the [capital worksheet](templates/career-capital-allocation-model.md) | Contingent income equals $0 in operating plan |
| [5. Protect](docs/battle-the-beast-legal-pathways.md) | Rights, consent, AI, publicity, youth safety; choice-and-consequence issue spotting through *Battle the Beast* | [Rights envelope](templates/rights-envelope.md), [split draft](templates/split-sheet.md), pathway decision record, risk list | Professional review where required |
| [6. Deliver](templates/delivery-checklist.md) | Technical package, public page, owned distribution | Fictional capstone package | [Rubric](ASSESSMENT-RUBRIC.md) passed; unresolved items visible |

## Choose-your-path legal practice

Use [Battle the Beast legal pathways](docs/battle-the-beast-legal-pathways.md) before the fictional capstone. The exercise connects branching narrative decisions to source tracing, collaborator terms, permission scope, provenance, and stop-for-review gates. It teaches issue spotting—not legal advice or clearance.

## Professional-resource programming

**MW-001 — Making Waves** is a proposed listening/demonstration module derived from the project's own programming record and informed by Producer Dojo / ill.Gates as an external professional resource. It uses the same canonical program for web, education, and live-event embodiments. Third-party course, newsletter, recording, or teaching materials are not reproduced or treated as cleared.

See `docs/program-making-waves.md` and `docs/event-programming.md`.

## Learning objectives

A learner can separate evidence from inference; distinguish composition, master, performance, publicity, and platform rights; define roles without erasing authorship; plan cash without treating forecasts as money; prepare versions, credits, metadata, stems, and handoffs; protect private evidence; and leave a platform without losing the archive or canonical identity.

## Evidence of completion

A charter, creative brief, story/music map, budget, cash ledger, contributor record, rights envelope, delivery manifest, accessibility review, platform-exit plan, and unresolved-issues log.


## Interactive narrative writer path

The curriculum now includes an interactive-narrative specialization using **[Inpatient Corridors: The Yellow Door](https://github.com/ibloud/inpatient-corridors-review)** as a concrete case study. See [Interactive Narrative Writer Path](docs/interactive-narrative-writer-path.md) for the Ink → compiled story → inkjs/browser workflow, source tracing exercise, controlled narrative modifications, playtesting, and original-story capstone. The case study is educational and independent; it does not imply third-party affiliation, endorsement, participation, or permission.