Event programming architecture

Purpose

The event layer uses the same canonical program records as the educational and web layers. It does not create a separate rights universe.

Rule: one program, multiple embodiments.

Current programming candidate

MW-001 — Making Waves

Format: listening lab / audio demonstration / workshop / discussion

External professional resource: Producer Dojo / ill.Gates

Relationship status: professional resource; prospective collaboration only. No endorsement, attachment, or partnership is represented.

Event embodiment

MW-001-LIVE is the live-event embodiment of the canonical MW-001 program.

It may be presented as:

Shared program record

The live version inherits:

from docs/program-making-waves.md.

Event rights gate

Before announcing, recording, or commercially exploiting an event, verify:

Area Evidence required
Presenter Written participation/appearance terms as applicable
Audio examples Ownership/license/permission sufficient for the actual use
Composition Sync/public-performance rights as applicable
Master Master-use/public-performance rights as applicable
Venue Venue/event permissions and recording rules
Brand Permission for names, logos, or co-branding
Audience Notice/consent or other applicable basis for recording
Recording Rights to edit, publish, distribute, and monetize
Education Any third-party teaching materials separately cleared
Sponsorship Written sponsor terms and deliverables

A missing item remains Pending until documented.

Recording rule

A recorded event is a distinct exploitation of the live program. Event attendance or presentation does not, by itself, establish perpetual rights to publish the recording.

The recording should receive its own evidence record:

MW-001-MEDIA

That record should identify:

Business handoff

Once an event is proposed commercially, connect the program record to:

No commercial relationship is implied until accepted terms are documented.

Relationship discipline

Producer Dojo / ill.Gates and Lex Nova are modeled consistently as professional resources.

The distinction is important:

resource → reference → proposed program → prospective relationship → executed agreement

The repository should never silently skip a step.

Download Markdown source · Presentation does not indicate legal review or clearance. See the document's stated status.

PIXIE