Example
How to run a coding-bootcamp capstone when the demo date cannot hold every feature
Four polished feature ideas are easier to discuss than the unreliable import that can erase the whole demonstration. Anika and her team must cut live import, contain it behind a prepared dataset, or spend the last integration day stabilizing it.
Ship an honest capstone demo with one complete user journey, explainable technical choices, and no borrowed confidence
The honest user journey the team promises to demonstrate
Define one end-to-end journey as the finish line
Build work that protects that journey before the freeze
Choose whether live import is cut, contained, or stabilized
Keep the actual freeze clock beside the three import paths
Reproducible tests and working paths the team can show
Preserve the login path as tested working evidence
Turn the existing failure evidence into a limitation note the team can defend
Keep the prepared dataset as option evidence; freeze it only if the team records contain
Hold the scored rubric language used in the import decision
Hold the three reproducible failures that govern cut, contain, or stabilize
Handoffs and copy the team still owns before anyone else is waiting
Keep presentation copy with the teammate who owns it
In You.one’s Superboard view, the Capstone demo Board separates the demo promise, next build work, working evidence, team handoffs, and what is genuinely ready.
Open Cut, contain, or stabilize live import as the Room with the Import decision note, reproducible failures, freeze clock, rubric, and working login.
After an explicit request, Ava can organize only the visible evidence without writing assessed work, fabricating tests, or interpreting the rubric as authority. Anika and her teammates own the code, attribution, testing, scope, and demo.
The demo needs one reliable journey, not ten hopeful features
The work has a clear center: Ship an honest capstone demo with one complete user journey, explainable technical choices, and no borrowed confidence.
Organizing the evidence does not authorize the software to decide: 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. Authority does not move to the software: Anika and her teammates own the code, attribution, testing, scope, and every claim made in the demo.
Available today
Name the work in plain language
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 something already awaiting another person. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| One journey that works end to end | Demo promise | Define one end-to-end journey as the finish line |
| Cut, contain, or stabilize live import | Build next | Choose whether live import is cut, contained, or stabilized |
| Login path works | Working evidence | Preserve the login path as tested working evidence |
| Draft the import limitation note | Working evidence | Turn the existing failure evidence into a limitation note the team can defend |
| Draft the presentation-copy handoff | Team handoffs | Keep presentation copy with the teammate who owns it |
| Dataset we could freeze if contain is chosen | Working evidence | Keep the prepared dataset as option evidence; freeze it only if the team records contain |
| Demo rubric: coherent journey over feature count | Working evidence | Hold the scored rubric language used in the import decision |
| Ten days to demo; one integration day remains | Build next | Keep the actual freeze clock beside the three import paths |
| Import failure cases | Working evidence | Hold the three reproducible failures that govern cut, contain, or stabilize |
Available today
Capstone demo: separate the kinds of attention
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.
The Lists use Anika's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Anika has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Demo promise | The honest user journey the team promises to demonstrate |
| Build next | Build work that protects that journey before the freeze |
| Working evidence | Reproducible tests and working paths the team can show |
| Team handoffs | Handoffs and copy the team still owns before anyone else is waiting |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Anika has made visible around “Cut, contain, or stabilize live import.” Anika supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Anika, watch other work on her own, or contact anyone.
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: in “Cut, contain, or stabilize live import,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
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.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Cut, contain, or stabilize live import” from the visible evidence. Ava can work from the context Anika deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Anika's call remains explicit: Anika and her teammates own the code, attribution, testing, scope, and every claim made in the demo.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | 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 | Keep Anika's request and Ava's attributed response with the work |
| Pulse | Open decision: Anika and her teammates will choose whether to cut, contain, or stabilize live import |
Build only enough Board to make the next decision
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.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Name the journey | Write the one user path the demo must complete |
| 2. Reproduce the risk | Record three import failures before debating features |
| 3. Read the rubric | Separate scored coherence from backlog ambition |
| 4. Record the import call | Open one Room, compare cut, contain, or stabilize, and record exactly one path |
| 5. Cut, contain, or stabilize live import | Freeze a prepared dataset only after contain is chosen; otherwise cut or stabilize as recorded and document the truthful limit |
Where this example stops
- This is a fictional example, not a customer story.
- 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.