# Making Waves — canonical program record

**Program ID:** MW-001  
**Status:** Proposed project programming / professional-resource integration  
**Owner of this project record:** 50 Ways to Leave Another / Loptr Lab  
**External professional resource:** Producer Dojo / ill.Gates  
**Relationship:** Professional resource; potential future collaborator/partner. No partnership or endorsement is claimed.

## 1. Purpose

**Making Waves** is a 50 Ways listening and demonstration format about how signals interact and how deliberate listening can reveal what changed.

The project record is an original programming layer. It is not a reproduction of Producer Dojo course material, newsletter copy, lesson files, recordings, branding, or other proprietary material.

## 2. Source / reference boundary

Producer Dojo / ill.Gates is documented here as a professional resource whose public educational ecosystem is relevant to the subject.

The source layer may inform the project's research and programming. Any protected source material remains outside the public repository unless permission establishes otherwise.

**Rule:** source attribution is not a license.

The project should use its own language, demonstrations, examples, sequencing, visual treatment, exercises, and event production.

## 3. Core learning experience

The audience hears the behavior before being given a recipe.

### Demonstration sequence

1. **Hear It** — hear two signals separately.
2. **Add It** — hear them together and compare the combined result.
3. **Change It** — alter one signal or its polarity and listen for the difference.
4. **Isolate It** — demonstrate a controlled comparison that exposes what changed.
5. **Apply It** — use a production tool or process and listen specifically for its audible effect.
6. **Name It** — explain the underlying audio concept after the listener has heard it.
7. **Transfer It** — connect the listening method to creative decision-making beyond the demonstration.

The exact audio assets should be original project assets or separately cleared materials.

## 4. Embodiments

One canonical program may be embodied as:

| ID | Embodiment | Status |
| --- | --- | --- |
| MW-001-WEB | Web lesson / article | Proposed |
| MW-001-INTERACTIVE | Browser listening experiment | Proposed |
| MW-001-EDU | Workshop / curriculum module | Proposed |
| MW-001-LIVE | Live event segment | Proposed |
| MW-001-MEDIA | Recorded audio/video version | Proposed |
| MW-001-PARTNERSHIP | Producer Dojo / professional-resource collaboration | Prospective only |

These are uses of one program record, not separate claims of ownership over third-party material.

## 5. Live event format

**Format:** listening lab + demonstration + facilitated discussion

**Suggested run of show:**

- Opening: establish the listening question.
- Demonstration A: separate signals.
- Demonstration B: combined signals.
- Demonstration C: controlled polarity/processing change.
- Audience A/B: ask what changed before naming the technique.
- Discussion: move from audible behavior to production decision.
- Application: audience identifies a change in a new example.
- Closing: document the takeaway and point to the learning materials.

### Event production controls

Before public performance or recording:

- identify all audio/music assets;
- clear third-party recordings and compositions as applicable;
- obtain presenter/performer permissions;
- obtain participant release/recording permissions where required;
- clear venue and event-media requirements;
- confirm brand/name/logo permissions for any co-branded use;
- document whether the event is educational, promotional, paid, licensed, or sponsored;
- preserve the final run of show and asset list.

## 6. Business pathways

Potential embodiments include:

- paid workshop;
- festival or conference session;
- educational licensing;
- co-produced class;
- sponsored demonstration;
- recorded educational media;
- podcast/radio segment;
- professional-development series;
- cross-platform programming.

These are planning options, not commitments.

Any paid collaboration with Producer Dojo / ill.Gates should be separately scoped for deliverables, compensation, ownership/license terms, credits, publicity, recording, distribution, and termination.

## 7. Legal controls

Do not treat:

- a public newsletter;
- a public course description;
- a public website;
- a social post;
- a marketplace listing; or
- a professional relationship

as permission to reproduce protected material or represent a party as attached.

If Producer Dojo / ill.Gates supplies original materials, instruction, recordings, trademarks, likeness, or other protected assets, obtain the appropriate written permission/license before the intended use.

## 8. Evidence record

The canonical evidence chain is:

**professional resource → public source/reference → project interpretation → original demonstration → program embodiment → event/media use → rights clearance**

Each transition should retain its own evidence. The existence of the upstream source does not automatically clear the downstream embodiment.

## 9. Cross-links

- docs/professional-resources.md — external resource relationship model
- PROVENANCE.md — evidence classes and source status
- SOURCES.md — public-source verification
- RIGHTS-AND-CLEARANCE.md — rights gates
- CURRICULUM.md — educational integration
- FACILITATOR-GUIDE.md — facilitation controls