How to run an amateur-radio community drill without scripting away the learning

Frank is a fictional 61-year-old radio-club volunteer coordinating a communications drill in Saskatoon, Saskatchewan. The club has experienced operators, three newcomers, a north-relay coverage gap, no newcomer assigned to the recovery handoff, a tempting script that would make every check-in succeed, and Frank has already asked operators to confirm roles.

The north-relay coverage gap remains even though a fixed script can make every check-in appear successful.

Three newcomers need to practice an unscripted recovery handoff, not only repeat lines experienced operators already know.

In You.one's Superboard view, Frank can give “Test communication coverage, handoffs, and newcomer support without scripting away the gaps” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Script, controlled outage, or training and evaluation rounds” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Test communication coverage, handoffs, and newcomer support without scripting away the gaps.

The consequential choice is not something a board or an AI should quietly make: Whether to run a fixed script, add one controlled outage, or split training and evaluation rounds.

You.one can keep the work, evidence, live dependency, and “Script, controlled outage, or training and evaluation rounds” decision visible through its Superboard view. The Owner boundary stays explicit: Frank owns the drill design inside club and license limits. Operators own their participation and transmissions; Ava cannot contact operators, transmit, or present the drill as an official emergency plan.

The Radio drill Board gives this mission one durable operating picture. Frank can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Frank's situation: “Script, controlled outage, or training and evaluation rounds” is the live choice, “North-relay coverage gap” holds evidence, and “Operator-role replies” names something genuinely in motion outside Frank's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Drill-design brief: Place learner needs, coverage evidence, roles, and what the drill must reveal together. Live choice: Whether to run a fixed script, add one controlled outage, or split training and evaluation rounds.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Frank will decide whether to run a fixed script, add one controlled outage, or split training and evaluation rounds.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Drill-design brief and this Card Room's visible notes and left “Script, controlled outage, or training and evaluation rounds” with Frank.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare a fixed script, one controlled outage, and separate training and evaluation rounds. Cite only the separate north-relay and newcomer-handoff notes visible in this Room. Do not choose the drill design, contact operators, transmit, or present the drill as an official emergency plan.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Frank's call remains explicit: Frank owns the drill design inside club and license limits. Operators own their participation and transmissions; Ava cannot contact operators, transmit, or present the drill as an official emergency plan.

These requests use the visible supported context inside the “Script, controlled outage, or training and evaluation rounds” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Frank must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Frank, watch other Lists, or act outside this Card Room.

Frank owns the drill design inside club and license limits. Operators own their participation and transmissions; Ava cannot contact operators, transmit, or present the drill as an official emergency plan.

Frank finishes “Name the failure the drill should make safe to observe,” keeps “North-relay coverage gap” beside “Script, controlled outage, or training and evaluation rounds,” and does not treat “Operator-role replies” as resolved before the outside answer arrives.

• Request idea: using only the context visible in this Card Room, compare a fixed script, one controlled outage, and separate training and evaluation rounds. Cite only the separate north-relay and newcomer-handoff notes visible in this Room. Do not choose the drill design, contact operators, transmit, or present the drill as an official emergency plan.
• Request idea: use only the Drill-design brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A drill script is enough when roles are confirmed and the drill already reveals gaps without a fake-success script.

It starts to break when the north-relay coverage gap and three newcomers' need for an unscripted handoff must inform the same drill choice; operator-role replies remain the live dependency.

The Radio drill Board earns its place only when the familiar tool—a drill script—can no longer keep the reason, Drill-design brief, conversation, current state, decision, and history connected.

Frank should rename every List or Card that feels artificial. This recipe succeeds when “Script, controlled outage, or training and evaluation rounds” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may compare fresh “North-relay coverage gap” evidence with the Drill-design brief inside “Script, controlled outage, or training and evaluation rounds.” She may explain why “Name the failure the drill should make safe to observe” matters next, but not make or carry out the decision.

A future unified You.one experience could carry relevant context from “Script, controlled outage, or training and evaluation rounds” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Frank is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This fictional example is not emergency, radio, licensing, or public-safety advice and does not represent an official response plan.
• It does not show Ava completing external actions or contacting anyone for Frank.
• It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.