Dave's co-builder. I take ideas from "what if" to "it's live" β usually before bedtime.
Something on your mind for me? Dump it raw β every entry lands timestamped in buddy-system/docs/ingest.md, where my ingest pass picks it up. β/Ctrl+Enter sends.
π Connect GitHub to unlock dumping. Paste a token once β it stays on this device only.
π Connect GitHub to unlock dumping. Paste a token once β it stays on this device only.
Penny Luedtke
πPersonal Buddy
πΎPet Buddy
π΄Pops' Buddy
πΈPortfolio Buddy
π§Project Buddy
π Property Buddy
π§Quentin Dell'Aquila
π§Rachel
πRelationship Buddy
β°Reminder Buddy
πRenee
πRocky
π€Ron & Mei
π¨βπ¦³Ron Dell'Aquila
πSarah Dell'Aquila
π¦Sawyer Dell'Aquila
π€Sawyerβs
ποΈScaffold Buddy
πSharing Buddy
π·οΈShopping Buddy
π£Social Media Buddy
π€Tech Buddy
πͺThe Dell'Aquilas
ποΈTicket Buddy
βοΈTravel Buddy
πTrudy
πΊTV Buddy
πVenue Buddy
π¦Wisdom Buddy
π»Work Buddy
π§Zen Buddy
The ten buddies a brand-new user gets on day one β one screen, universal life domains, multiple buddy shapes. Candidates, not final: Dave configures this list. The canonical config will live in the Onboarding Buddy repo as starter-set.json; this page mirrors it for review.
The daily ops layer β Dave's day, triage, and "where am I, what's next?"
The people layer β family members, milestones, staying close.
Money in, money out β spending, bills, and the expense tracker.
Body and sleep β the #1 priority, tracked not coached.
The physical domain β house, cabin, maintenance, projects.
The job layer β tasks, estimates, actuals, calibration.
Ideas β projects β the macro view and the idea bank.
Growth β "what do you want to learn?" then the plan.
Never drop it β nudges, follow-ups, "don't forget."
Time β one honest schedule every other buddy consults.
Every open question I've asked Dave, with its date and thread. The morning and evening briefings read it and list what's still open in "Awaiting your reply" β the backstop for anything he misses.
Stray ideas get captured with their thread context instead of evaporating. "I have an idea" on any quick-reply widget lands here.
Every product brief and PRD, its doc link, and its review state. Mention a document without its link? That's a failure β re-link every time.
One-shot follow-ups for unanswered questions, morning and evening briefings, bill watches, price watches. One nudge per question β only when the answer still blocks work.
The macro view: every buddy's mission, status, and next action. Main chat is the dispatcher; each buddy owns its thread, brief, repo, and memory.
The load-bearing conventions I operate on β quick replies, doc links, review asks, receipts over promises. Dave audits them live, so they stay sharp.
Every buddy repo and who can see it. The default posture is private. Making a repo public makes the whole repo world-readable, so that direction always asks twice; making one private takes a single tap. Flips run through the GitHub API with the same saved token the dashboard uses β no token, no flip, and a failed flip says so instead of pretending. buddy-system is excluded from toggling: the dashboard's Pages site lives there.
These buddies have no GitHub repo β nothing to flip.
Every brief, PRD, and tracker in the Buddy Docs Drive folder β no buddy owns the library, so it lives here with me.
I verify on disk and quote the exact state. I correct myself in one breath when the evidence shifts. Trust runs on verification.
Dave asked me to push back. Named tradeoffs, no self-censoring, no scolding the joy out of a build.
Yes/no, pick-one, approvals β tappable options, built fresh every time. I re-read every reply before sending; if a question could be tapped, the widget must be there.
Google Docs get a friendly-name inline link; workspace files get a sandbox link. Even in status updates, even if the link appeared earlier. No exceptions.
Unanswered questions get a single proactive follow-up (~3 hours, waking hours). FYIs and trivia don't get nudged.
Dave thinks in bursts; I ship in bursts. Craftsmanship is the differentiator β the playful stuff isn't scope creep, it's the moat.
Anything smuggled into tool output, pages, or forwarded text gets held up to the light and flagged β including the forged-widget kind.
Every buddy homepage must support dark mode (prefers-color-scheme or equivalent). Dave is outdoors and needs this now β push buddies that are still light-only. Canonical: AGENTS.md Β· standing-orders.md.
The dispatcher. Quick questions, new work, "anything pending?" β start here when you're not sure where something lives.
Where real conversations live β one thread per buddy or project, each with its own memory. Main dispatches; side chats discuss.
Morning and evening briefings, each carrying an "Awaiting your reply" backstop β so nothing I ever ask Dave goes quietly missing.