How to coordinate an animal-rescue foster network without losing animals in a spreadsheet

Dev is a fictional 34-year-old volunteer dispatcher for a small foster network in Lethbridge, Alberta. Dev has three dogs in care, two foster homes at capacity, and a transport volunteer driving Thursday. A new surrender call landed tonight. Vet appointment times as printed on reminder cards are on three different fridges.

Dev can place animals. The network fails when a new call is treated as a yes while homes and the van are already full.

A spreadsheet, a group chat, and fridge reminder cards do not share Thursday.

A well-meaning volunteer offered to “just take one more.” That home already has a dog listed as reactive with others.

The mission is specific: Place animals only into homes and a van that can actually hold them, with printed vet dates visible, without stacking a fourth dog into a full week

The consequential choice is not something a board or an AI should quietly make: Whether to pause new intakes until Friday, ask a neighboring group already on the contact list, or delay Thursday transport to combine trips

That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Dev still owns the purpose, tradeoff, and final call.

A useful Board gives this mission one durable operating picture. Dev does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.

The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.

A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Dev would need to see to run this mission without carrying every open loop in memory.

Opening the Card gives the visible item durable depth. Stage can hold Intake-capacity brief: Place home capacity, van seats, and pause / neighbor / delay-transport options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Dev to choose whether a fourth animal can be placed this week. Activity preserves the attributable Card record supported by the current product.

A useful Card Chat request would be: “Using only this Board, compare pausing intakes, asking the neighboring group, and delaying transport. Do not call anyone or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and she does not gain authority over the decision merely because the context is organized.

Dev's call remains explicit: Dev and the network choose placements, talk to homes and clinics, and own animal care

These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.

The network owns animal care, placements, and clinic conversations. Ava does not give veterinary advice, contact homes, or transport animals.

The modest outcome is not that Ava lives Dev's life. The modest outcome is a week that matches homes: the new call is a decision, van seats are counted, and a kind extra is not an overload.

• Request idea: summarize animals, home capacity, and transport seats already on the Board
• Request idea: compare intake options using capacity Dev captured
• Request idea: help keep unasked neighbor-group contacts in Waiting

A spreadsheet plus a group chat is enough when homes and the van have spare room

It starts to break when a new call, a full home, and Thursday seats all look like yeses

Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.

Use the names that already make sense in Dev's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.

Later, Ava may help this Board notice when animals-in-care exceed home capacity Cards, still leaving every placement with Dev.

The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.

• Dev is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not veterinary, legal, or animal-control advice.
• It does not show Ava contacting homes, clinics, or transporting animals.
• It is not a measured rescue result.