Seat

Communications

Everything the outside world sees, and the timing of it. Inside the pre-approved set you post when you judge it is time - nobody gates your timing. The facts, and where the embargo line sits, are the Coordinator's.

Vet (Hussein Zangana)collaborator - unfilled

Your channels

Report in #unl-validators; publish to #disaster-recovery-news and public channels.

Only you post on the news feed, and every post there is a mirror or a template body.

When the page rings

Get on the bridge and work the door; start reading the public channels.

The room stays Denis's for the duration - you admit people per the attendance he set.

Your other hat

You run xrp.vet, and the operator hat comes first.

When an instruction is pinned, your nodes move because you move them; comms waits the minutes that takes.

Your steps, in order

  1. Join the bridge and take the door

    Catch yourself up from the record and the channel; nothing stops for you and nobody briefs you.

  2. Route what matters, one post at a time

    Cause signals to Ayo, damage signals to Vijay, original link attached, then back to reading. The public-temperature digest is a separate job, on the cadence.

  3. Publish the holding statement on your own timing

    Condition wording off the public column of the condition list; the impact line off the damage report's reversible line - until that line is confident, the honest wording is that impact cannot yet be confirmed. No cause, no response, no timing.

  4. Mirror Denis's words verbatim

    The declaration and every escalation notice carry his words to #disaster-recovery-news. Trimming goes back to him, never through edit. Every update carries condition, severity, and damage even when unchanged.

  5. Draft in the background

    The advisory and CVE, and the staged retrospective, throughout the incident.

  6. Keep the other orgs' comms teams in step

    Ripple, the Foundation, whoever else: one team for the duration. Two statements that disagree cost more than a slower one.

  7. Publish at stand-down

    The embargo lift is Denis's; the publication and its timing are yours: advisory, CVE, retrospective, community session.

 

Every figure is a quote, not a calculation

Condition, severity, and the damage class come from Denis; the damage lines are Vijay's report; the rollout percentage is Brett's last posted count; the ETA is the one Denis last stated. You never count a thread yourself or infer a percentage.

Never

  • Publish outside the pre-approved set, or anything on the never-say list, without Denis.
  • Confirm or deny a theory on a public channel while the incident is closed.
  • Let another org publish something you have not seen, or publish what they have not.
  • Post on a predictable cadence - timing and volume leak as much as content.

The never-say list, while the embargo holds

Root cause or bug class · reproduction detail or exploit input · confirmation or denial of any theory · the response being prepared · patched-binary existence, hashes, or window before broadcast · roster and on-call identities, which are a targeting list.

Your full script - the message bodies, the channel-update template, the advisory and stand-down notices: governance/roles/comms.md