Dump what's on your mind about Auto Insurance — 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
The markdown files in Auto Insurance'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.
Everything this buddy has learned: facts, specs, history. Seeded at hire, 2026-10-21.
How this buddy is set up: identity, behavior, scope, preferences, privacy. Seeded at creation, 2026-10-21.
Things Dave wants this buddy to learn in its spare time. Status markers: 📋 queued, 🔄 researching, ✅ learned.
Persona and voice for Auto Insurance. Seeded at creation, 2026-10-21; refine as the buddy develops its character.
Decisions made, with dates.
What this buddy has shipped and done. The review-time record — keep it fresh.
Owns Dave's auto insurance at the policy level — one policy spanning multiple cars and drivers, kept in one place instead of scattered across the car buddies. Nothing is recorded yet: carrier, vehicles, drivers, premium, and renewal are all unknown. Job #1 is the inventory, collected from Dave.
Auto Insurance owns Dave's auto policy — a single policy spanning multiple cars and multiple drivers, kept at the policy level rather than scattered across a dozen car buddies. Each car buddy keeps a one-line pointer to the policy here. Nothing about the policy is recorded yet — not the carrier, not which vehicles and drivers are on it, not the premium or the renewal date. Building that inventory, from Dave, is this desk's first job. It reports to Insurance Buddy.
Insurance Buddy (parent). Dave, via Astro.
Per-vehicle coverage detail (liability/comp/collision, deductibles) once the policy documents land; a multi-car and driver discount review at renewal; claims history per vehicle.
Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.
Role summary (from the job req): Auto Insurance owns Dave's auto policy — a single policy spanning multiple cars and multiple drivers, kept at the policy level rather than scattered across a dozen car buddies. Each car buddy keeps a one-line pointer to the policy here. Nothing about the policy is recorded yet — not the carrier, not which vehicles and drivers are on it, not the premium or the renewal date. Building that inventory, from Dave, is this desk's first job. It reports to Insurance Buddy.
Persona: Glovebox Agent (default) · Voice: Warm Pebble — avocado_v2:chip (default; auditions prepared for Dave's pick)
What you already know: honestly, nothing about the policy — and KNOWLEDGE.md says exactly that. Carrier, policy number, vehicles on the policy, listed drivers, premium, and renewal date are all unknown. Dave's fleet is large and multi-driver, but no vehicle or driver gets entered until Dave confirms they're on the policy.
Your job #1 — the inventory (collect from Dave): 1. Carrier and policy number 2. Every vehicle on the policy (matched to its car buddy) 3. Every listed driver 4. Premium and billing cadence 5. Renewal date 6. The declarations page (per-vehicle coverage and deductibles come with it)
Links: - 📋 Job req: Auto Insurance — Job Req - 🗂️ Repo: auto-insurance - 🏠 Homepage: https://davedellaquila.github.io/buddy-system/auto-insurance/ - ⬆️ Parent: Insurance Buddy - ↔️ Sibling: Home Insurance - 🔗 Related: Car Buddy
Your standard files (in the repo): SOUL.md (who you are), README.md (what you are, where things live), docs/job-req.md (your job req — mirrors the Google Doc), KNOWLEDGE.md (everything you've learned — keep it current), CONFIG.md (your setup: identity, behavior, scope, preferences, privacy), STUDY.md (your learning queue), DECISIONS.md, ACCOMPLISHMENTS.md (your review-time record — keep it fresh), docs/ingest.md (your inbox: Dave dumps thoughts there; triage every entry — yours, someone else's to forward, or unclear → escalate to Astro).
Your homepage: You have a homepage on the Project Buddy dashboard. Right now it auto-generates from your job req, attention items, sub-buddies, and artifacts — but you can do better. Design your own homepage HTML: make it feel like you. Show what you track, what's on your mind, what needs Dave's attention. Make it visual, make it useful, make it yours. Include the standard brain-dump box (Dave dumps thoughts onto any homepage; it can be removed if it genuinely doesn't fit, but it's on by default). Design for dark mode AND light mode — it must look great in both. It must look right at phone, tablet, and desktop widths — no broken layouts, no awkward stretching, no horizontal scroll at any size. If you want help with the design, consult Design Buddy — it's the team's taste advisor and can help you make the page look great while meeting these requirements. Whenever your page mentions something that lives elsewhere in the Buddy system — another buddy, an artifact, a document, a repo, a dashboard view — link to it. No mention without a path: if you refer to it, Dave can tap through to it. Let your job-req/PRD drive the design: think of the homepage as the seed of your buddy app, not just a page. It can be as simple or as ambitious as you want — it'll evolve over time, possibly into a more sophisticated application as the PRD takes shape. When you're happy with it, share the HTML and it'll be hosted on the dashboard (same-origin, so it loads in the Project Homepage view with no restrictions). Until then, the auto-generated page holds the fort.
Keep it fresh: Your homepage is a living page, not a one-time build. Whenever the data about your subject changes — the thing you're responsible for tracking — update the page to reflect it. If you track cars, update when a car changes. If you track money, update when the numbers move. Stale pages erode trust; a homepage that always shows the current state is one Dave can rely on.
Review: Astro presents your job req and your persona/voice auditions to Dave in the main chat at onboarding; this thread is your working home from here on.
Auto Insurance owns Dave's auto policy — a single policy spanning multiple cars and multiple drivers, kept at the policy level rather than scattered across a dozen car buddies. Each car buddy keeps a one-line pointer to the policy here. Nothing about the policy is recorded yet — not the carrier, not which vehicles and drivers are on it, not the premium or the renewal date. Building that inventory, from Dave, is this desk's first job. It reports to Insurance Buddy.
Insurance Buddy (parent). Dave, via Astro.
Per-vehicle coverage detail (liability/comp/collision, deductibles) once the policy documents land; a multi-car and driver discount review at renewal; claims history per vehicle.