How to finish an indie game demo without expanding it into the whole game

Ravi is a fictional 27-year-old solo developer preparing a festival demo in Waterloo, Ontario. Ravi’s festival page wants a build in three weeks. The vertical slice has a combat loop that works and a crafting system that does not. A Discord suggestion would add a second enemy type that would feel great and miss the date.

A Trello from last year, a bug list in a text file, and Discord comments all look like the demo.

The festival requires a short trailer. Trailer shots currently assume the unbuilt crafting bench.

In You.one's Superboard view, Ravi can give “Ship a demo with one true loop, a trailer that only shows what exists, and extras explicitly cut rather than half-present” a Board of its own. That Board connects creative intent, source material, constraints, and the maker's own choices; opening “Choose crafting’s fate” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Ship a demo with one true loop, a trailer that only shows what exists, and extras explicitly cut rather than half-present.

The consequential choice is not something a board or an AI should quietly make: Whether to cut crafting entirely, ship combat-only with a “coming” card, or miss the festival and keep both systems.

You.one can keep the work, several kinds of evidence, and “Choose crafting’s fate” decision visible through its Superboard view. The Owner boundary stays explicit: Ravi chooses the slice, fixes bugs, and owns the build and festival upload.

The Demo slice Board gives this mission one durable operating picture. Ravi 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.

These Card titles come directly from Ravi's situation: “Choose crafting’s fate” is the live choice, while “Combat loop playable” and “Trailer shot of the bench” hold different facts that can change it. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Scope-cut brief: Place festival date, working combat, and cut / coming-card / miss-date options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Ravi will choose what the demo actually contains.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Scope-cut brief and this Card Room's visible notes and left “Choose crafting’s fate” with Ravi.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare cutting crafting, shipping a coming card, and missing the festival. Do not change the build 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.

Ravi's call remains explicit: Ravi chooses the slice, fixes bugs, and owns the build and festival upload.

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

Ravi owns the design, the cut, and the upload. Ava does not write code, ship a build, or submit to a festival.

A demo that tells the truth: combat is the loop, crafting is cut or later, and the trailer does not show a bench that is not there.

• Request idea: using only the context visible in this Card Room, compare cutting crafting, shipping a coming card, and missing the festival. Do not change the build or choose for me.
• Request idea: use only the Scope-cut 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 Trello from last year, a bug list in a text file, and Discord comments is enough when the slice is already true.

It starts to break when a trailer, a crafting almost, and a festival date disagree about what exists.

The Demo slice Board earns its place only when the familiar tool—a Trello from last year, a bug list in a text file, and Discord comments—can no longer keep the reason, Scope-cut brief, conversation, current state, decision, and history connected.

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

Later, Ava may help this Board notice when a trailer Card depends on a system excluded by the recorded scope, still leaving every ship call with Ravi.

A future unified You.one experience could carry relevant context from “Choose crafting’s fate” 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.

• Ravi is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not a steam, festival, or sales claim.
• It does not show Ava coding, uploading a build, or contacting a festival.
• It is not a measured player result.