Creators, interviews, and the unofficial spokesperson

A register that only covers the site is a register of the thing you already edit. The damage is usually elsewhere: a founder improvising on a live stage, a well-followed creator translating “review in progress” into “audited,” a community moderator answering “when moon” with a date. Those sentences inherit the brand whether or not they inherited the sheet.

This is why creator operations sit next to the register, not in a separate “growth” folder. Each creator on an RCA Pad campaign has a written disclosure requirement, a pre-approval step, a prohibited-claims list drawn from the register, geographic restrictions, payment terms, publication evidence and a takedown clause. Identity is known. Disclosure history is known. There is no roster seat without an archived policy.

Pre-approval is the unfashionable part. It means the post is read against the register before it is published, not after it has been screenshot. Teams that skip this step are always surprised. They should not be. A creator is paid to be fluent. Fluency without a prohibited list is how “independent review” becomes “fully secure” in forty characters.

The founder interview is the other leak. Brief the founder from the live rows. Give them the permitted sentences and the three words they must not say. Record the interview if you can. If a sentence escapes that is not on the register, treat it as an incident: pause the clip, pull the claim, notify the approver, archive what ran, record the line. Charm is not a control.

Creator misconduct and unsubstantiated claims are stop-the-line events. Pause the channel. Do not negotiate the sentence in public.

Desk Seven, on the Vellum blotter, drafted a global-retail thread with return language. The post was not published. The roster seat went to hold. The approver was notified. That is a successful incident. Success, here, is boring. Nobody outside the house should have seen it.