Example
How a tutoring business can run a semester without double-booking the table
Lauren can teach. If the buffer slot becomes a thirteenth standing student, every snow day becomes a refund argument.
Hold a semester of standing slots, honest payments, and one makeup buffer, without converting the waitlist into overcrowding
Slot cap, buffer rule, and rented-room hours
Keep the cap and makeup slot visible beside demand
Each weekly seat with subject and payment status
Show a seat that is named but not currently happening
People who are not yet a slot
Compare sibling, Friday group, and keep-buffer options
Hold the ask without placing it on the grid
Rental evenings and what the table holds
Mark the empty-looking slot as reserved on purpose
Possible offers Lauren has not made yet
Prepare an offer without treating it as parent demand
Lauren is an explicitly fictional portrait, not a customer or testimonial.
The Semester slots Board gives one mission a visible field; the Choose Thursday’s buffer Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Semester slots needs an operating picture
Lauren is a fictional 43-year-old independent math tutor running after-school sessions in Boston, Massachusetts. Lauren has twelve weekly students, a waitlist of four, and a classroom she rents two evenings. Midterms will compress demand. A parent asked to add a sibling in the only remaining Thursday slot that is also her buffer for makeup lessons.
A paper grid, a payment app, and email waitlist notes do not share a picture of Thursday.
A student who has missed two weeks is still on the grid as if the seat were full and paid.
In You.one's Superboard view, Lauren can give “Hold a semester of standing slots, honest payments, and one makeup buffer, without converting the waitlist into overcrowding” a Board of its own. That Board connects customer promises, operating evidence, capacity, and the owner's judgment; opening “Choose Thursday’s buffer” creates a Room for its evidence, discussion, state, and decision.
A waitlist is not capacity; a buffer slot is not empty
The mission is specific: Hold a semester of standing slots, honest payments, and one makeup buffer, without converting the waitlist into overcrowding.
The consequential choice is not something a board or an AI should quietly make: Whether to give Thursday’s buffer to the sibling, open a short Friday group of three waitlist students, or keep the buffer and stay at twelve.
You.one can keep the work, evidence, and “Choose Thursday’s buffer” decision visible through its Superboard view. The Owner boundary stays explicit: Lauren chooses enrollment, talks to parents, and owns teaching and refunds.
Available today
Semester slots: one Board shape to adapt
The Semester slots Board gives this mission one durable operating picture. Lauren can use familiar language instead of translating the situation into project-management jargon. Its five 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.
| List | What belongs here |
|---|---|
| Mission | Slot cap, buffer rule, and rented-room hours |
| Standing students | Each weekly seat with subject and payment status |
| Waitlist | People who are not yet a slot |
| Room and materials | Rental evenings and what the table holds |
| Offers to draft | Possible offers Lauren has not made yet |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Lauren's situation: “Choose Thursday’s buffer” is the live choice, “Thursday 4:30 makeup buffer” holds evidence, and “Student with two missed weeks” is still work Lauren controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Twelve seats and one buffer | Mission | Keep the cap and makeup slot visible beside demand |
| Choose Thursday’s buffer | Waitlist | Compare sibling, Friday group, and keep-buffer options |
| Thursday 4:30 makeup buffer | Room and materials | Mark the empty-looking slot as reserved on purpose |
| Sibling request: grade 8 algebra | Waitlist | Hold the ask without placing it on the grid |
| Student with two missed weeks | Standing students | Show a seat that is named but not currently happening |
| Draft the Friday group offer | Offers to draft | Prepare an offer without treating it as parent demand |
Available today
Available today: Choose Thursday’s buffer becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Capacity brief: Place the buffer rule, waitlist, and sibling / Friday-group / keep-buffer options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Lauren will choose how waitlist demand is handled.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Capacity brief and this Card Room's visible notes and left “Choose Thursday’s buffer” with Lauren.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare giving away the buffer, opening a Friday group, and staying at twelve. Do not email parents or choose for me.” 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.
Lauren's call remains explicit: Lauren chooses enrollment, talks to parents, and owns teaching and refunds.
| Surface | Job in this example |
|---|---|
| Stage | Capacity brief: Place the buffer rule, waitlist, and sibling / Friday-group / keep-buffer options on one page |
| Chat | Keep Lauren's request and Ava's attributed response with the work |
| Pulse | Open decision: Lauren will choose how waitlist demand is handled |
| Activity | Ava compared the options in Card Chat using the Capacity brief and this Card Room's visible notes and left “Choose Thursday’s buffer” with Lauren |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose Thursday’s buffer” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Lauren 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 Lauren, watch other Lists, or act outside this Card Room.
Lauren owns enrollment, pricing, and parent conversations. Ava does not email families, take payment, or teach.
A semester with an honest cap: Thursday’s buffer is a decision, missed weeks are visible, and the waitlist is not secretly the schedule.
- Request idea: using only the context visible in this Card Room, compare giving away the buffer, opening a Friday group, and staying at twelve. Do not email parents or choose for me.
- Request idea: use only the Capacity 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 paper grid plus a payment app may still be enough
A paper grid plus a payment app is enough when every student comes every week.
It starts to break when a buffer, a sibling ask, and two missed weeks all look like the same Thursday.
The Semester slots Board earns its place only when the familiar tool—a paper grid plus a payment app—can no longer keep the reason, Capacity brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Lauren should rename every List or Card that feels artificial. This recipe succeeds when “Choose Thursday’s buffer” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the cap and buffer | Empty is not the same as available |
| 2. Card standing students | Including missed weeks and payment status |
| 3. Keep a waitlist list | Names who are not yet seats |
| 4. Map room hours | Rented evenings as a constraint |
| 5. Choose Thursday’s buffer | Open a Room before the buffer disappears |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when standing Cards exceed the cap on the Mission, still leaving every enrollment with Lauren.
A future unified You.one experience could carry relevant context from “Choose Thursday’s buffer” 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.
What this realistic example does not claim
- Lauren is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not educational, licensing, or tax advice.
- It does not show Ava emailing parents or taking payment.
- It is not a measured student or revenue result.