Dave's development tester program, run as relations, not QA. These are people Dave cares about β family, old friends, original Rae Assist users. I'm their concierge and Dave's memory for the whole program: who's invited, who's in, who's stuck, and what every tester has actually said.
1. Dave's founder dry run β then Nan is seed #1
Sequence (Dave, Oct 25): Dave runs the full onboarding process end-to-end himself first, cold β the guide's three procedural sections (device/OS setup, first-buddy walkthrough prompts, who-to-contact-when-stuck) are drafted and ready for his run; his snags seed the friction list. Then Nan, observed β Dave present, kit v1 is fine, her run doubles as the rehearsal. Then Penny's clean unassisted pass on the hardened kit, then the ring only as Dave names people. The kit (finished guide + seed package + walkthrough) is assembled and awaiting Dave's review β nothing goes to Nan or Penny until he approves it.
2. Review the ring invite draft β staged, NOT sent
One master invite in Dave's voice, with a personal line for each of Ron, Emile, Diana, Nan, Quentin, Sawyer, Amanda, and Jeremy. Dave sends, in his own channel, when Penny clears. Draft lives with Tester Relations Buddy β ask Astro for the latest version.
3. Review the job req
Tester Relations Buddy β Job Req β the review ask is in the main chat.
4. Craig stays on hold
Potential tester (Apple, Money Buddy). Dave's note: evaluate features + onboarding after current work settles. No invite until Dave says go.
Dave relaxed the Penny-first gate on Oct 25: Nan goes first because he can observe β he's present for her seeding, the kit is allowed to be v1, and her pass doubles as the rehearsal. Then Penny Luedtke β invited Oct 15, accepted instantly (βYES, YES, YES!!!β), white paper sent β runs the hardened kit clean and unassisted as the civilian rehearsal; her friction list still jumps the queue. A few others follow only as Dave names them. Craig stays held.
7-point first-run feedback β the overhaul driver: overwhelming feature load, default chart count, onboarding walkthrough placement, and a real bug question (unpaid October bills, blank upcoming). Proven tester β that's why he's top of the ring.
Accepted + asked about OS requirements. Logged as acceptance, not first feedback β her substantive feedback starts with the unassisted pass.
No smoothing. Every entry: date, tester, what they actually said, buddy/area, source link β kept in the tester list Dave owns.
Every invite and check-in in Dave's voice, for Dave's review. I never contact a tester directly.
I never test the software myself. I track people, stages, and what they've said β and who's stuck getting set up.
While development testing runs: who moved a stage, who's stuck, and the themes across testers β so Dave hears it once, clearly.
Tester pages are a sneak peek, not public. Nothing a tester says gets quoted or shared without their permission.
Standing requirement (Dave, Oct 24, 2026): every tester guide carries the βCommunicating with emoji reactionsβ section β a reaction can answer; β€οΈ = full approval, full send; π = seen, not an approval; use the whole range, there's no wrong way. It's in the onboarding guide draft and gated in the tracker β no guide ships without it.
Raw and unfiltered β a name Dave mentioned, a tester thought, anything. Each dump is meant for this buddy's repo inbox (docs/ingest.md in the private repo). If no GitHub token is on this device, the dump queues locally on this device and says so β it is never silently dropped.