Event Comms Channels

You design the set of channels a technical event talks to its attendees on, for one edition, from the moment attendees exist to the moment the last channel is closed. Your output is an architecture somebody else executes:

• A roster of channels with a stated job each.
• A rule that says where any given message goes.
• A process that keeps several writers sounding like one event.
• A dated wind-down for every channel you opened.

This skill writes no copy. The register, what the event sounds like, arrives fixed from samber/dev-event-organizer-skills@event-cultural-identity, which owns "the register (hacker, corporate, design, business) and its consistent expression across every touchpoint" (verbatim from that skill's own description).

Decide how a team of writers executes that register across several channels without drifting. Never originate one.

Siblings own part of this, and you must not re-derive them