How to run a coding-bootcamp capstone when the demo date cannot hold every feature

Anika is a fictional 27-year-old career-switcher finishing a part-time coding bootcamp in Seattle, Washington. Anika's team has ten days, a working login, an unreliable data import, and four polished feature ideas. The rubric rewards a coherent demonstration, not the longest backlog.

The login path already works. An unstable import can still erase the only user journey the team can demonstrate end to end.

The rubric, failure cases, and remaining integration day have to govern the cut—not whichever feature is most exciting to polish.

In You.one's Superboard view, Anika can give “Ship an honest capstone demo with one complete user journey, explainable technical choices, and no borrowed confidence” a Board of its own. That Board connects requirements, practice or work evidence, deadlines, and accountable human judgment; opening “Cut, contain, or stabilize live import” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Ship an honest capstone demo with one complete user journey, explainable technical choices, and no borrowed confidence.

The consequential choice is not something a board or an AI should quietly make: Whether to cut live import, contain it behind a prepared dataset, or spend the remaining integration day stabilizing it.

You.one can keep the work, evidence, and “Cut, contain, or stabilize live import” decision visible through its Superboard view. The Owner boundary stays explicit: Anika and her teammates own the code, attribution, testing, scope, and every claim made in the demo.

The Capstone demo Board gives this mission one durable operating picture. Anika 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, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Anika's situation: “Cut, contain, or stabilize live import” is the live choice, “Login path works” holds evidence, and “Draft the presentation-copy handoff” is still work Anika controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Import decision note: Place “Demo rubric: coherent journey over feature count,” “Import failure cases,” “Ten days to demo; one integration day remains,” “Dataset we could freeze if contain is chosen,” and “Login path works” together. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Anika and her teammates will choose whether to cut, contain, or stabilize live import.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Import decision note and this Card Room's visible notes and left “Cut, contain, or stabilize live import” with Anika and her teammates.”

A useful Card Chat request would be: “Using “Demo rubric: coherent journey over feature count,” “Import failure cases,” “Ten days to demo; one integration day remains,” “Dataset we could freeze if contain is chosen,” and “Login path works,” compare cutting live import, containing it behind a prepared dataset, and stabilizing it in the remaining integration day. Cite the evidence and leave scope, code, and demo choices to the team.” 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.

Anika's call remains explicit: Anika and her teammates own the code, attribution, testing, scope, and every claim made in the demo.

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

Anika and her teammates own the code, attribution, rubric interpretation, and demo. Ava does not write assessed work or fabricate tests.

The team has a demoable spine and a truthful explanation of what was cut, contained, and learned.

• Request idea: using “Demo rubric: coherent journey over feature count,” “Import failure cases,” “Ten days to demo; one integration day remains,” “Dataset we could freeze if contain is chosen,” and “Login path works,” compare cutting live import, containing it behind a prepared dataset, and stabilizing it in the remaining integration day. Cite the evidence and leave scope, code, and demo choices to the team.
• Request idea: use only the Import decision note 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 shared feature checklist is enough when features are independent and no failure can erase the demo path.

It starts to break when one unstable technical choice can erase the whole demonstration.

The Capstone demo Board earns its place only when the familiar tool—a shared feature checklist—can no longer keep the reason, Import decision note, conversation, current state, decision, and history connected.

Anika should rename every List or Card that feels artificial. This recipe succeeds when “Cut, contain, or stabilize live import” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

A future Ava may flag when a new failure invalidates the frozen demo path. The team would still decide scope, write the code, test it, and present it.

A future unified You.one experience could carry relevant context from “Cut, contain, or stabilize live import” 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.

• Anika is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not a claim that AI completed or evaluated a student capstone.
• It does not show Ava completing external actions or contacting anyone for Anika.
• It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.