How to run a student robotics competition build without letting the parts list become the plan

Sofia is a fictional 16-year-old robotics-team build lead in Phoenix, Arizona. Sofia's team has a drivetrain that works, an arm that slips under load, one missing sensor shipment, and a scrimmage in nine days.

A missing sensor and a slipping arm are not equivalent backlog items. One is a dependency; the other is measured evidence about the mechanism in hand.

Every extra arm motion also consumes the drive-practice time needed to make the simpler cycle reliable and safe.

In You.one's Superboard view, Sofia can give “Arrive at the scrimmage with one reliable scoring cycle, documented failure modes, and safe work ownership” a Board of its own. That Board connects requirements, practice or work evidence, deadlines, and accountable human judgment; opening “Choose the arm scope” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Arrive at the scrimmage with one reliable scoring cycle, documented failure modes, and safe work ownership.

The consequential choice is not something a board or an AI should quietly make: Whether to cut the raise-and-place motion after lift, rework the current mechanism, or run a limited-load scoring cycle before drive practice; the sensor shipment remains a separate dependency.

You.one can keep the work, evidence, live dependency, and “Choose the arm scope” decision visible through its Superboard view. The Owner boundary stays explicit: Sofia, teammates, and adult mentors own design, testing, equipment, and the robot; adult mentors approve safe work, and competition officials own event rules.

The Scrimmage build Board gives this mission one durable operating picture. Sofia 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 Sofia's situation: “Choose the arm scope” is the live choice, “Arm slips under load” holds evidence, and “Sensor shipment” names something genuinely in motion outside Sofia's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Arm decision brief: Place “Second scoring motion: raise and place after lift,” “Lift motion works before raise-and-place,” “Arm slips under load,” “Reserve drive-practice blocks,” “Adult-mentor safety limit,” “Sensor shipment,” and “One scoring cycle nine days from now” together. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Sofia, her teammates, and adult mentors will choose the arm scope.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Arm decision brief and this Card Room's visible notes and left “Choose the arm scope” with Sofia, her teammates, and adult mentors.”

A useful Card Chat request would be: “Use “Second scoring motion: raise and place after lift,” “Lift motion works before raise-and-place,” “Arm slips under load,” “Reserve drive-practice blocks,” “Adult-mentor safety limit,” “Sensor shipment,” and “One scoring cycle nine days from now” to compare cutting the raise-and-place motion after lift, reworking the mechanism, and running a limited-load scoring cycle before drive practice. Keep the sensor shipment as a separate dependency. Do not design or operate the robot, approve safety, or invent test results.” 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.

Sofia's call remains explicit: Sofia, teammates, and adult mentors own design, testing, equipment, and the robot; adult mentors approve safe work, and competition officials own event rules.

These requests use the visible supported context inside the “Choose the arm scope” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Sofia 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 Sofia, watch other Lists, or act outside this Card Room.

Sofia, teammates, and adult mentors own design, testing, equipment, and the robot; adult mentors approve safe work, and competition officials own event rules. Ava does not operate equipment or approve safety.

The team knows which scoring cycle it is protecting and what it will not attempt at the scrimmage.

• Request idea: use “Second scoring motion: raise and place after lift,” “Lift motion works before raise-and-place,” “Arm slips under load,” “Reserve drive-practice blocks,” “Adult-mentor safety limit,” “Sensor shipment,” and “One scoring cycle nine days from now” to compare cutting the raise-and-place motion after lift, reworking the mechanism, and running a limited-load scoring cycle before drive practice. Keep the sensor shipment as a separate dependency. Do not design or operate the robot, approve safety, or invent test results.
• Request idea: use only the Arm decision 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 parts spreadsheet is enough when every part independently makes the robot better.

It starts to break when mechanism reliability, practice time, and a missing shipment compete.

The Scrimmage build Board earns its place only when the familiar tool—a parts spreadsheet—can no longer keep the reason, Arm decision brief, conversation, current state, decision, and history connected.

Sofia should rename every List or Card that feels artificial. This recipe succeeds when “Choose the arm scope” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may flag when a shipment or new load test changes the arm decision. The team and mentors would still design, build, test, and approve safe operation.

A future unified You.one experience could carry relevant context from “Choose the arm scope” 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.

• Sofia is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not engineering, electrical, or youth-safety advice.
• It does not show Ava completing external actions or contacting anyone for Sofia.
• It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.