How to run a genealogy research project without confusing a tree app with sources

Edith is a fictional 63-year-old family historian tracing one confusing great-grandparent in Sydney, Nova Scotia. Edith has a tree app full of hints, a folder of census images, and a cousin who sent an unsourced story. A research trip to an archive is possible in May. She keeps adding distant branches because the hints are easy.

A tree app, a census folder, and an email story all look like progress.

Chasing a distant branch feels like research and postpones the archive appointment.

In You.one's Superboard view, Edith can give “Answer one written question about the confusing great-grandparent with sources attached, and treat hints and stories as leads until they earn a citation” a Board of its own. That Board connects the project's purpose, materials, experiments, and the maker's judgment; opening “Choose archive, park story, or cite existing” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Answer one written question about the confusing great-grandparent with sources attached, and treat hints and stories as leads until they earn a citation.

The consequential choice is not something a board or an AI should quietly make: Whether to spend May at the archive on that question, park the cousin story, or spend the month citing what she already has.

You.one can keep the work, evidence, and “Choose archive, park story, or cite existing” decision visible through its Superboard view. The Owner boundary stays explicit: Edith chooses the question, cites sources, and owns any archive visit.

The One research question Board gives this mission one durable operating picture. Edith 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 Edith's situation: “Choose archive, park story, or cite existing” is the live choice, “Census images already in a folder” holds evidence, and “Tree-app hint pile” is still work Edith 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 Research-path brief: Place the written question, existing images, and archive / park / cite options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Edith will choose a path that serves the written question.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Research-path brief and this Card Room's visible notes and left “Choose archive, park story, or cite existing” with Edith.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare using May at the archive, parking the cousin story, and citing what is already in the folder. Do not contact archives 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.

Edith's call remains explicit: Edith chooses the question, cites sources, and owns any archive visit.

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

Edith owns the research, citations, and any archive visit. Ava does not contact archives, invent ancestors, or attach unsourced facts.

A project with a question: the cousin story is a lead, the census folder is work to cite, and May is aimed or parked.

• Request idea: using only the context visible in this Card Room, compare using May at the archive, parking the cousin story, and citing what is already in the folder. Do not contact archives or choose for me.
• Request idea: use only the Research-path 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 tree app plus a hints sidebar is enough when the question is already sourced.

It starts to break when an unsourced story, a May archive day, and easy distant hints share one person.

The One research question Board earns its place only when the familiar tool—a tree app plus a hints sidebar—can no longer keep the reason, Research-path brief, conversation, current state, decision, and history connected.

Edith should rename every List or Card that feels artificial. This recipe succeeds when “Choose archive, park story, or cite existing” 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 hint Card is being treated as a source, still leaving every citation with Edith.

A future unified You.one experience could carry relevant context from “Choose archive, park story, or cite existing” 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.

• Edith is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not genealogical proof, legal identity, or a claim about any real family.
• It does not show Ava contacting archives or adding people to a tree.
• It is not a measured research result.