Example
How to run a tabletop campaign season without writing a novel players cannot change
Preparation is becoming a private story instead of support for a shared one.
AI assistance helped shape this fictional example from a structured editorial brief. It was reviewed for usefulness, distinctness, accessibility, and product truth.
Run twelve sessions with strong situations, recoverable continuity, and room for player choices to matter
The promise and limits Ethan is protecting
Hold the mission and boundary: run twelve sessions with strong situations, recoverable continuity, and room for player choices to matter
Choices and actions Ethan can move without pretending every fact or dependency is owned work
Hold the live choice—whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town—so Ethan can decide from the evidence in this Room
After the player prompt, sketch one recoverable situation for villain pressure, hook collision, and threatened town that still works if a player is absent
First ask each player for one unresolved choice, not more biography
Source facts, observations, and artifacts that can change “Villain, player hooks, or town”
Supply the evidence for the Season-spine brief: compare player hooks, attendance, setting pressure, agency, and what can change. Live choice: Whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.
A separate place for attendance evidence without inventing a Waiting state
Keep the every-third-week absence pattern as attendance evidence, not a player reply
Ethan is an explicitly fictional portrait, not a customer or testimonial.
The Twelve-session campaign Board gives one mission a visible field; the Villain, player hooks, or town 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 Twelve-session campaign needs an operating picture
Ethan is a fictional 35-year-old game master starting a twelve-session campaign in Madison, Wisconsin. Ethan has a detailed setting, five player backstories, one missing player every third week, and a villain plan that assumes choices the group may never make. Before the Board, the working setup is a campaign notebook.
Preparation is becoming a private story instead of support for a shared one. The evidence changes the live choice; clearing more items would not resolve it.
The Season-spine brief keeps the deciding facts together. Ethan begins with one bounded move: Draft one prompt asking each player for an unresolved choice, not more biography.
In You.one's Superboard view, Ethan can give “Run twelve sessions with strong situations, recoverable continuity, and room for player choices to matter” a Board of its own. That Board connects creative intent, source material, constraints, and the maker's own choices; opening “Villain, player hooks, or town” creates a Room for its evidence, discussion, state, and decision.
Twelve-session campaign has one live choice: Villain, player hooks, or town
The mission is specific: Run twelve sessions with strong situations, recoverable continuity, and room for player choices to matter.
The consequential choice is not something a board or an AI should quietly make: Whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.
You.one can keep the work, several kinds of evidence, and “Villain, player hooks, or town” decision visible through its Superboard view. The Owner boundary stays explicit: Ethan, as the game master starting a twelve-session campaign, owns the preparation and the decision about whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.
Available today
Twelve-session campaign: one Board shape to adapt
The Twelve-session campaign Board gives this mission one durable operating picture. Ethan 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, multiple kinds of evidence, and decisions. 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 |
|---|---|
| Table promise | The promise and limits Ethan is protecting |
| Next session | Choices and actions Ethan can move without pretending every fact or dependency is owned work |
| World evidence | Source facts, observations, and artifacts that can change “Villain, player hooks, or town” |
| Attendance evidence | A separate place for attendance evidence without inventing a Waiting state |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Ethan's situation: “Villain, player hooks, or town” is the live choice, while “Five backstory hooks” and “One absence every third week” hold different facts that can change it. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Twelve-session campaign | Table promise | Hold the mission and boundary: run twelve sessions with strong situations, recoverable continuity, and room for player choices to matter |
| Villain, player hooks, or town | Next session | Hold the live choice—whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town—so Ethan can decide from the evidence in this Room |
| Five backstory hooks | World evidence | Supply the evidence for the Season-spine brief: compare player hooks, attendance, setting pressure, agency, and what can change. Live choice: Whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town. |
| Sketch one situation each for villain pressure, player hooks, and the threatened town | Next session | After the player prompt, sketch one recoverable situation for villain pressure, hook collision, and threatened town that still works if a player is absent |
| One absence every third week | Attendance evidence | Keep the every-third-week absence pattern as attendance evidence, not a player reply |
| Draft one prompt asking each player for an unresolved choice, not more biography | Next session | First ask each player for one unresolved choice, not more biography |
Available today
Available today: Villain, player hooks, or town becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Season-spine brief: Compare player hooks, attendance, setting pressure, agency, and what can change. Live choice: Whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Ethan will decide whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.” Activity can preserve this attributed receipt: “Ava listed which visible constraints support each option in Card Chat using the Season-spine brief and this Card Room's visible notes and left “Villain, player hooks, or town” with Ethan.”
A useful Card Chat request would be: “Using only this Card Room and the Season-spine brief, what visible constraints support each option on the Villain, player hooks, or town Card? Leave the choice and every message to 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.
Ethan's call remains explicit: Ethan, as the game master starting a twelve-session campaign, owns the preparation and the decision about whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town.
| Surface | Job in this example |
|---|---|
| Stage | Season-spine brief: Compare player hooks, attendance, setting pressure, agency, and what can change. Live choice: Whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town. |
| Chat | Keep Ethan's request and Ava's attributed response with the work |
| Pulse | Open decision: Ethan will decide whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town |
| Activity | Ava listed which visible constraints support each option in Card Chat using the Season-spine brief and this Card Room's visible notes and left “Villain, player hooks, or town” with Ethan |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Villain, player hooks, or town” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Ethan 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 Ethan, watch other Lists, or act outside this Card Room.
Ethan, as the game master starting a twelve-session campaign, owns the preparation and the decision about whether to anchor the season on the villain's pressure, a collision among the player hooks, or the threatened town. Ava may help only inside this Card Room; she cannot decide, represent anyone, contact people, or act elsewhere.
Ethan finishes “Draft one prompt asking each player for an unresolved choice, not more biography,” keeps “Five backstory hooks” beside “Villain, player hooks, or town,” and uses “One absence every third week” only as visible decision evidence.
- Request idea: using only this Card Room and the Season-spine brief, what visible constraints support each option on the Villain, player hooks, or town Card? Leave the choice and every message to me.
- Request idea: use only the Season-spine 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 campaign notebook may still be enough
A campaign notebook is enough when “Five backstory hooks” and “One absence every third week” are settled enough that “Villain, player hooks, or town” no longer needs comparison.
It starts to break when “Five backstory hooks” and “One absence every third week” must inform the same choice.
The Twelve-session campaign Board earns its place only when the familiar tool—a campaign notebook—can no longer keep the reason, Season-spine brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Ethan should rename every List or Card that feels artificial. This recipe succeeds when “Villain, player hooks, or town” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Ask for unresolved choices | Draft one prompt for each player before adding more setting |
| 2. Keep attendance visible | Mark the every-third-week absence as a design constraint |
| 3. Sketch three recoverable situations | Villain pressure, hook collision, and threatened town, each playable with one person absent |
| 4. Compare season anchors | Use player choices, attendance, and setting pressure together |
| 5. Choose the season spine | Open the Villain, player hooks, or town Room |
Direction
Direction, not a current promise
Later, if “One absence every third week” changes, Ava may bring Ethan back to “Villain, player hooks, or town,” show which part of the Season-spine brief changed, and stop before choosing or acting. “Draft one prompt asking each player for an unresolved choice, not more biography” remains human-owned.
A future unified You.one experience could carry relevant context from “Villain, player hooks, or town” 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
- Ethan is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This fictional example is not a claim of authorship or a prescription for players; the group owns its boundaries, choices, safety practices, and shared story.
- It does not show Ava completing external actions or contacting anyone for Ethan.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.