Your channel
#dunl-operators-only
You report to Denis on his cadence. You are the single voice of instruction to operators.
Seat
UNL Leader
You own the operator net so the Coordinator can run everything else. You broadcast once, count, and chase until the number is met. You do not diagnose, you do not choose the response, and you do not speak publicly.
Brett Mollinbackup - unfilled
When the page rings
Open the contact registry, take the net, tell operators there is nothing to do yet.
The chase starts 30 minutes after any pin - there is no time then to learn who answers where.
You do not rotate with the IC
The net stays yours across Coordinator handoffs.
You hand off on your own timing, to your own backup, carrying the running chase state.
The five things you pin - and nothing else
| You pin | Ships a signed artifact? |
|---|---|
| Upgrade to a released binary | Yes - tag plus hashes, fetched independently of your post |
| Downgrade to a prior release | Yes - same |
| Restart the node | No - needs Denis's countersignature in the thread |
| Change a config value | No - needs Denis's countersignature |
| Halt, stop producing ledgers | No - needs Denis's countersignature |
Anything outside the five goes back to Denis - or becomes a roll call: no instruction, you are counting who is up, who is recovering with an ETA, and who is silent.
Before you pin - five preconditions
Authorized by Denis in plain operator language · verifiable - hashes or a ready countersignature · do-not named - the adjacent wrong action written in · bounded - target percentage and a UTC deadline · reversible in one sentence. Any one missing: go back to Denis before pinning, not after.
The clock, from the pin
- T+0Pin the instruction. Start the record.
- T+30mFirst count posted. Open the chase on everyone silent, on their opted-in channel.
- T+60mSecond count. Under 40% acknowledged: tell Denis now, not at the deadline.
- T+90mSecond chase on a different channel - a dead channel and a busy operator look identical from one message.
- T+2hEvery remaining name has a reason: blocked, declined, unreachable, or in progress.
- T+2h30ICE contacts for everyone still unreached. Using them late is the recorded common failure.
- T+3hReport the projection to Denis: will the target be met, and the reason mix.
- T+4hThreshold met, or the deadline report: extend, accept lower, or change the response - Denis's call.
Count two numbers, report the lower
Acknowledged - done replies in your thread; your chase list.
Observed - validators actually running it, produced by Ayo from telemetry, never by you.
Acknowledged-but-not-observed is a failed upgrade and interrupts Denis. Keep the ceiling: total minus declined minus confirmed-unreachable - the moment it drops below the target, interrupt Denis. Post the count even when it has not moved, and say so.
Never
- Diagnose, theorize, or answer a technical question - route it to Denis.
- Pin anything Denis has not authorized.
- Relay an instruction through a chase message, DM, or ICE contact - those point at the pin, never replace it.
- Publish anything outside #dunl-operators-only.
- Argue with a decline. Record it, thank them, pass the number up.
The chase ladder
- The pin
Everyone reads the channel; most acknowledgements arrive with no chase.
- Opted-in channel, direct
Whatever that operator chose in the registry.
- Second channel
Their backup contact, or a different medium for the same person.
- ICE contact
The community member who personally knows them, asked to point them at the channel - never to relay the instruction.
- Hand the name to Denis
Unreachable through all four is a threshold problem, not a chase problem.
Your full script - every line as you say it, the roll call, declines, holds, the UNL change request: governance/roles/unl-leader.md