Dump what's on your mind about Projects Buddy — raw and unfiltered. Each dump lands in the buddy's repo (docs/ingest.md) as a timestamped entry — or saves on this device until a repo is linked and a token is connected.
🔒 Connect GitHub to unlock dumping. Paste a token once — it stays on this device only.
Enter dumps it · Shift+Enter for a new line · Images shrink to 1600px wide before upload — the original stays in your library
No files yet.
The markdown files in Projects Buddy's repo, baked into this page when it was generated — tap a file name and its contents open right below it; open as many as you like at once. No sign-in and no fetching: the words are right here. To change a file, edit it in the repo — the page picks it up next time it is generated.
How this buddy is configured: identity, persona, voice, scope, preferences, privacy. (Project Buddy predates the new_project.py seeding, so this file was created Nov 3, 2026 to bring its records in line with the fleet convention.)
One place for all of Dave's ideas and projects — fast capture, an idea bank with statuses (New → Considering → Active → Parked → Done/Dropped), promote-to-project with next actions, and lightweight review nudges.
Read the full brief · Google Doc · PRD Draft v1
The macro view: davedellaquila.github.io/buddy-system — built from davedellaquila/buddy-system.
Draft v1 — 2026-10-09. For Dave's review. This document describes how the Buddy system fits together as of October 2026. It is descriptive, not aspirational: where the plan outruns reality, that's called out.
The Buddy system is Dave's personal operating system for ideas and projects. One buddy = one problem domain (a person, a property, a project, a workflow). Each buddy is a small, consistent package: a conversation, a brief, a repo, and a home page. ~40 buddies exist as of 2026-10-09, growing by the day.
Buddy Suite is the shared layer: common branding, design language, monetization, and marketing across the family. Individual buddies (Money Buddy, Cabin Buddy, Party Buddy, …) are the products; Buddy Suite is what makes them feel like one family.
| # | Component | What it is | Where it lives |
|---|---|---|---|
| 1 | Chat thread | The buddy's conversational home. All discussion, decisions, and reviews happen here. First message is always the INIT summary (executive summary + links to brief, repo, related docs, parent/children). | Muse side chats (private 1:1) |
| 2 | Product brief | Canonical description: the idea, the problem, revenue potential, room for growth, v1 scope, open questions. Dave reviews every brief before anything else is built. | Google Docs in the Zuki Docs Drive folder |
| 3 | GitHub repo | One private repo per buddy (davedellaquila/<slug>). Holds code today; will hold the knowledge base (KNOWLEDGE.md, DECISIONS.md) once the Scaffold Buddy template lands. The drill currently stamps README.md + docs/brief.md on creation. |
github.com/davedellaquila |
| 4 | Dashboard | The macro view of the whole system: every buddy's status, next actions, and home page. Views: Tree, Org chart, Outline, Projects, Plans, Manifest. | buddy-tree repo → static site at davedellaquila.github.io/buddy-tree |
| 5 | The drill | The automation that creates components 1–3 (+ registry/memory entries) from a project name + idea. Codified as the project-buddy skill; implemented by new_project.py. |
~/workspace/skills/project-buddy/ |
| 6 | Scaffold Buddy (planned) | The repo template: README.md, KNOWLEDGE.md, DECISIONS.md, stamped into every new repo. Brief exists; not yet wired into the drill. |
Brief in Zuki Docs |
buddies.json in the buddy-tree repo is the source of truth for the
dashboard. build.py generates the static index.html from buddies.json
(+ plans.json for the Plans view, + buddy-tree.html for style/fragments).
A build stamp (YYYYMMDD.HHMM) is baked into every generated page.
Registry schema per buddy:
id, name, parent, kind, tagline, mission, status, statusClass,
brief (Google Doc URL), repo (repo slug), docs[], icon (emoji),
photos[], attention[] (review/action items with dates)
parent is a buddy id or null (only Project Buddy has null). 41 of 42
buddies have a parent.kind is one of: root, personal, family, property, finance,
work, standalone, meta.attention[] is the review queue — items Dave needs to look at, each with
an id, date, and text.Rebuild + push after every registry change:
python3 build.py && git add -A && git commit -m "…" && git push origin master.
The dashboard is a static page — it resets on reload. State lives in three tiers:
buddies.json/plans.json, baked
into index.html at build time. Changing it means editing the registry
and rebuilding.<buddy-repo>/docs/notes.md (debounced ~900ms autosave
on input; whole-file replace via the contents API)
- Brain-dump ingest → <buddy-repo>/docs/ingest.md (appended as
timestamped entries; 2s debounce, Enter dumps immediately)
- Photos → <buddy-repo>/photos/<buddy-id>/ (HEIC auto-converted to
JPEG client-side)Write flow: textarea input → debounce → base64 encode → PUT
/repos/davedellaquila/<repo>/contents/<path> with the device token.
Without a token, repo-backed fields are disabled with an explicit warning —
nothing silently fails.
Two tokens, two trust domains. Never commingle them.
repo scope, created at github.com/settings/tokens/new. Entered once,
globally (not per buddy) in the dashboard; stored only in the device's
localStorage; sent only to api.github.com. Powers all repo-backed writes
from the page (notes, ingest, photos).gh CLI credential on the assistant's
machine. Used server-side by the drill: create/clone/push/rename repos.
Notably lacks the delete_repo scope (repo deletion stays manual).
This token must never be handed to the page, pasted into chat, or stored
anywhere Dave's browser can read.Buddies nest: one parent, many children. Examples (2026-10-09):
The model: knowledge flows both directions — children inherit the parent's knowledge base; parents see rollups from their children. Moves are made by telling the assistant ("move X under Y"), which updates the registry, dashboard, INIT summaries, and memory together.
Reality check: today the hierarchy is real in the registry and the dashboard views. The two-way knowledge flow (shared KNOWLEDGE.md / DECISIONS.md across parent and child) is the intent, pending the Scaffold Buddy template rollout.
ADR-1 — Static-first dashboard. The dashboard is a generated static site on GitHub Pages, not a web app. Rationale: zero hosting cost, trivially shareable via link, no backend to operate. Cost: no server-side persistence; everything dynamic happens in the browser or not at all.
ADR-2 — Repo as source of truth for shared content. Anything another human should see (shared notes, ingest log, photos) is written into the buddy's Git repo as plain files, not into a database. Rationale: durable, auditable, visible with repo access, no new infrastructure.
ADR-3 — Device-held credentials. The user's GitHub token lives only on their device (localStorage), entered once. Rationale: the static site has no backend to hold secrets; this keeps the credential out of every server log.
ADR-4 — Drill automation over manual setup. Every buddy is created by the same codified drill (thread + brief + repo + review + memory), not by hand. Rationale: Dave creates buddies constantly; consistency compounds.
ADR-5 — Briefs as Google Docs, not markdown. Product briefs and PRDs
live only as Google Docs in Zuki Docs. Dave doesn't use Word; .docx is
never created, not even as staging. Rationale: his rule, non-negotiable.
ADR-6 — Hierarchy with two-way knowledge flow. Parent/child nesting with knowledge flowing both directions (see §6). Status: model adopted; knowledge layer pending Scaffold Buddy.
README.md / KNOWLEDGE.md /
DECISIONS.md into every repo via the drill; backfill existing repos.alias field exists
in buddies.json today. Decide: add to the schema, or drop the idea.plans.json holds non-buddy plans (e.g. Amador
County Transport) with a looser schema. Should plans graduate into
buddies, or stay a separate concept?Project Buddy is the one place for every idea: fast capture, an idea bank with statuses, and lightweight project tracking for the keepers. It exists because ideas currently die in Muse chat transcripts — not searchable, no status, no nudges. V1 is for Dave, designed around how he works: bursts of building, side threads per topic, quick capture usually from the iPhone. This PRD turns the approved product brief into buildable requirements.
• Dave stops losing ideas: every idea lands in the bank within seconds of occurring to him.
• The bank earns a quick weekly glance (the review habit).
• At least one shipped thing traces back to “I put it in Project Buddy.”
FR-1 · Instant capture. Saving an idea takes seconds: a title plus optional notes. iPhone-first and dictation-friendly — capture happens on the go, often by voice.
FR-2 · The bank. Every idea in one searchable list, taggable. Each idea carries a status: New → Considering → Active → Parked → Done / Dropped. Nothing disappears silently; dropping an idea is a deliberate state, not deletion.
FR-3 · Promote to project. An idea graduates into a project with a simple next-action list — next actions, not Gantt charts.
FR-4 · Review nudge. A lightweight periodic prompt to revisit the bank and work the statuses. The habit without the nagging. (Exact cadence: see open questions.)
• Capture must feel instant (a few seconds, iPhone-first).
• Single user; no sharing or collaboration in v1.
• Simple, boring tech that Dave can maintain.
• Team collaboration or sharing.
• Time tracking, estimates, Gantt charts.
• Integrations with other apps (standalone until it earns them).
Form factor: standalone web app on the Finance Buddy pattern (Firebase backend, iPhone-first), or something else?
Buddy links: should ideas link into the other buddies (e.g. an idea becomes a Job Buddy lead or a task for another buddy)?
Nudge cadence: how pushy should the review nudge be — weekly? opt-in only?
Backfill: what happens to the ideas already living in Muse threads — manual import, assisted sweep, or fresh start?
• An idea can be captured from the iPhone in under 10 seconds.
• Every idea is findable by search; statuses are visible at a glance.
• Dropping an idea requires an explicit action; deleted-by-accident is impossible.
• The review nudge fires on schedule and is dismissible without guilt.
• At least one shipped project traces its origin to the bank.
M1: PRD approved; form factor decided.
M2: Capture + bank working for Dave on iPhone.
M3: Statuses, promote-to-project, review nudge live.
M4: First shipped thing traced back to the bank.
Dave generates ideas constantly — product ideas, business ideas, project ideas, “someday” ideas. Right now they go into Muse chat threads, which is a bad idea bank: conversations scroll away, ideas can’t be searched or sorted, there’s no sense of status (is this live? parked? dead?), and nothing ever nudges a good idea back into attention. Ideas die in the transcript.
One place to put every idea, then work the keepers into real projects. Fast capture (an idea should take seconds to save), a bank where ideas live with a status, and lightweight project tracking for the ones that graduate — next actions, not Gantt charts. Not Jira, not a second job: the smallest tool that keeps ideas alive until they’re done or deliberately dropped.
V1 is for Dave, designed around how he works: bursts of building, side threads per topic, quick capture usually from the iPhone.
• Instant capture: title + notes in seconds, iPhone-first, dictation-friendly.• The bank: every idea in one searchable list, taggable.• Statuses: New → Considering → Active → Parked → Done / Dropped. Nothing disappears silently; dropping is a deliberate state.• Promote to project: an idea becomes a project with a simple next-action list.• Review nudge: a lightweight periodic prompt to revisit the bank — the “idea review” habit, without nagging.
• Team collaboration or sharing• Time tracking, estimates, Gantt charts• Integrations with other apps (standalone until it earns them)
• Standalone web app on the Finance Buddy pattern (Firebase backend, iPhone-first), or something else?• Should ideas link into the other buddies (e.g. an idea becomes a Job Buddy lead or a Service Buddy task)?• How pushy should the review nudge be — weekly? opt-in only?• What happens to the ideas already living in Muse threads — manual import, assisted sweep, or fresh start?
Dave stops losing ideas. The bank gets a quick weekly glance. At least one shipped thing traces back to “I put it in Project Buddy.”
High — Dave asked for this to jump the queue (2026-10-09).
Canonical brief: Project Buddy — Product Brief (Google Doc, Zuki Docs).
A full mirror lives in this repo at PRODUCT_BRIEF.md; the PRD draft is mirrored at PRD.md.
Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.