# Working Memory — FAQ

Every answer below stands alone and is safe to quote out of context.
Canonical HTML version: https://workingmemory.yarbros.net/faq

## Who is behind Working Memory?

Rob Belcher is a product manager of over 20 years based in Austin, Texas, USA, who now builds the software he used to specify. He is AuDHD and writes about designing tools around executive function. He runs production apps at yarbros.net: YarMeals, YarDocs, YarMail, YarJobs and YarGo.

## What is Working Memory?

Working Memory is Rob Belcher's blog and portfolio at workingmemory.yarbros.net. It documents self-built household apps, the transition from product manager to builder, and the mistakes made along the way. Posts are published in full on the site and cross-posted to LinkedIn.

## What are the apps and what does each do?

Rob Belcher runs production apps at yarbros.net. YarMeals — Automates meal planning and grocery shopping for a family of 5. YarDocs — Labels, sorts, and files all the documents that come through a busy family’s week. YarMail — Not only filters and sorts the 1500 emails I get per week, but processes the ones that need action. YarJobs — AI coach that elicits deep career motivations and ideal job profiles and then scores and tracks postings from spotted to hired. YarGo — Curated features of all the sites in a native iOS app.

## Is he available for work?

Yes. Rob Belcher is open to senior and principal individual-contributor product roles where the person defining the product can also play a hands-on role in building it, remote or in Austin, and to collaborations on tooling for neurodivergent users. The fastest route is email: rbelcher@gmail.com.

## How does a product manager end up building production software?

Rob Belcher studied computer science engineering at Texas A&M and managed application development teams early in a career of over 20 years, so the ground was not unfamiliar — but he had not shipped production code himself in years. What closed the gap was pairing product judgment with AI coding tools, and treating memory — where decisions get written down — as the core of the system rather than the model. The apps run on Python, TypeScript, Postgres and agent orchestration, all operated by one person.

## What does AuDHD have to do with the software?

Every one of Rob Belcher's apps is built around three constraints that come directly from his executive function. Never ask the same question twice — decisions go into a ledger, not a person's head. The system initiates the work; the human reacts. Every action is reversible and logged. He treats those as accessibility requirements, not preferences.

## Can an AI agent contact him directly?

Not yet directly. Working Memory publishes a manifest describing the tools an assistant would use — profile, posts, app stats and a message tool — but the server behind it is not published, so there is nothing to install and no message tool to call. Everything the read tools would return is already plain text on the site: llms.txt, faq.md and the sitemap. To reach Rob Belcher today, email rbelcher@gmail.com.