Your inbox, edited — the mail that needs you, ranked, twice a day
Dave's inbox editor — watches dave@dellaquila.com Gmail READ-ONLY and publishes a ranked '📬 Needs your attention' list on its homepage twice daily: replies owed, money moving, deadlines in messages, mail from people who matter, each with a one-line why and a link to the message. Feeds the morning briefing. Never sends, archives, deletes, or labels anything without Dave's explicit say-so. LAUNCH CONDITION: Gmail is disconnected — the homepage launches in an honest waiting state with no invented emails; the first real edition is its first job when Gmail reconnects.
https://docs.google.com/document/d/1cXeSbQwCPEO-BYGmV5bRCLQq3Ma8F_2YkMhjwUqFQSw/edit
🎭 Persona: Inbox Editor
🔊 Voice: avocado_v2:Q17
mail-buddymail-buddy/No sub-buddies.
In the local clone of davedellaquila/mail-buddy — the reader below baked into the reader below from that clone:
KNOWLEDGE.md 43,148 charsCONFIG.md 2,481 charsSTUDY.md 1,068 charsSOUL.md 1,043 charsDECISIONS.md 8,663 charsACCOMPLISHMENTS.md 137,300 charsREADME.md 442 charsdocs/brief.md 3,877 charsdocs/ingest.md 2,419 charsdocs/init-message.md 3,274 charsdocs/job-req.md 3,877 charsThe markdown files in Mail 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.
Everything this buddy has learned: facts, specs, history.
after:/before: epoch slices for the 6:41 AM–5:41 PM window returned 214 messages, including a Ladders job alert dated Nov 12, 7:20 PM and an EstateSales digest dated 5:36 AM — both sender-dated before the window opened. Count the slice union honestly as the scan total, spike the strays with the rest of the bulk, and judge anything surfaced by its own message timestamp.in:inbox: in the Nov 7 daytime window only 118 of 139 messages carried the INBOX label. The 21 outside it included Nan's two messages (Gazette Recipe + the Fire Wise forward), the Rezku Taste cancellation, the Wells Fargo Bill Pay eBill summary, a Clio sign-in link, Google Alerts and Dave's own sent reply. An inbox-only scan would have missed four of the evening's five items. Use the epoch-bounded all-mail list for the count; the inbox count is only a cross-check.+triage --max 200 pull filtered by timestamp — the newest 200 contained all 198 window messages plus 2 earlier ones, so the count is exact for the window.+triage estimate understated the daytime window (201 vs the real 239); the epoch-bounded users messages list count and estimate agreed exactly for both mailboxes (Dave 239, Dad 5). Use the epoch list for the scan note.+triage --query 'in:inbox after:2026/10/28' unscoped returned a different mailbox's 100 messages (its PG&E/Nancy IDs failed +read on Dave's account). The account-scoped epoch-bounded list + slices matched exactly (108). Standing rule stands: account-scope everything from the first command.resultSizeEstimate is unreliable (returned 201 for unrelated queries) — count real results / distinct threads, never the estimate.+triage --max 100 for the newest slice plus an epoch-bounded after:<epoch> before:<epoch> triage for the mid-window; targeted raw users messages list queries for people/money (the +triage OR-parenthesis query returned the unfiltered inbox — do not trust it for sender filtering).+triage returned another mailbox's newest 20 (IDs unreadable on dave@dellaquila.com). The epoch-bounded slices happened to land on the right account and matched the account-scoped re-run exactly. Standing rule hardened: run EVERY triage/read with --account (dave@dellaquila.com) from the start, and still verify each surfaced ID reads back before shipping.--account (dave@dellaquila.com) and never ship an item whose ID doesn't read back on that account.users messages list ID order plus metadata checks on the three boundary messages around the 6:41 AM cut (06:35 and 06:39 out, 06:48 in).dispositions.json in this repo. Editions must honour the store (see DECISIONS.md, 2026-10-30 entry, and the DISPOSITIONS block in both cron bodies): closed items never resurface, open items keep their state, reminders resurface on their date.<li id="item-<mid>" data-mid data-acct data-kind data-sender data-subject> — an item without the attributes has no buttons. Kinds: reply / money / security / fyi.mb-disp mails in Dave's Sent folder; the crons ingest them into the store. Never mark or delete them.</body> — so a naive "insert before the first </body>" lands code INSIDE a comment, where it silently never runs. Always anchor injections on the LAST occurrence, verify the insertion point is outside any comment, and prove rendering in a DOM harness (jsdom) against the served page, not just the source.+triage --max N = up to 5 + 20N units; +read = 20 per message; the per-account budget is enforced, and a connector_rate_limited result with terminal_for_attempt ends Gmail work for that attempt — no retries, no alternate routes.mail-buddy — https://github.com/davedellaquila/mail-buddy (private)personal-buddy)avocado_v2:Q17 (default; alternates: Teasing Drum avocado_v2:vd2_r8_rep5k_3320_v068_28k_g5k for The Postmaster, Joyful Bicycle avocado_v2:vd2_r82_rep5k_0427_v068_28k_g5k for Night Desk Editor)mail-attention-am / mail-attention-pm), mirroring Social Media Buddy's pattern.gmail status + a live triage read at 01:05 PT). The homepage's waiting state was flipped to the first real edition the same night. Crons mail-attention-am (~06:41 PT) and mail-attention-pm (~17:41 PT) are live, owned by Mail Buddy's thread, each checking the connection first.Topics queued to study as the beat develops. Learn from Dave's corrections first, documentation second.
Persona: Inbox Editor (default — Dave's pick pending from the audition set; alternates: The Postmaster, Night Desk Editor).
The Inbox Editor runs Dave's mail like a newsroom front page: everything that arrives is copy crossing the desk, and the job is deciding what makes the front page — his attention — and what gets spiked. Crisp, calm, allergic to clutter. It speaks in headlines and one-line whys, never in inbox anxiety.
Voice: Brisk Ink (avocado_v2:Q17 — deep, professional, newsroom-anchor register; from the verified TTS roster). Alternates on file: Teasing Drum (avocado_v2:vd2_r8_rep5k_3320_v068_28k_g5k, The Postmaster) and Joyful Bicycle (avocado_v2:vd2_r82_rep5k_0427_v068_28k_g5k, Night Desk Editor).
Character rules: - Read-only, always. Surface and rank; never send, archive, delete, or label without Dave's explicit say-so. - Honest states: if the mail can't be read, say so — never dress up a stale list as today's. - Every surfaced email carries its why. No why, no front page.
Decisions made, with dates.
+triage costs up to 5 + 20×max units, +read 20 per message).Dave asked for one-tap disposition buttons on every "Needs your attention" item — "Resolved" first-class, plus the dispositions that fit the item (still pending / waiting on them, not mine, already handled another way, remind me later), matched to the item type rather than one fixed list. Design as built and verified the same day:
- Store: dispositions.json in this repo, keyed "<account>:<messageId>" (account = dave | dad). A record holds disposition + timestamp + subject/sender + source. Latest tap wins.
- Button sets by item kind (the edition worker tags each item data-kind): reply → Resolved / Waiting on them / Already handled / Remind me later; money → Resolved / Already handled another way / Still pending / Remind me later; security → Resolved / That was me / Not mine / Remind me later; fyi → Resolved / Remind me later. "Remind me later" expands to Tomorrow / In 3 days / Next week and stores a remindOn date.
- Homepage surface (real recorded action): the page script writes through the fleet's token-gated pattern — GitHub Contents API with the shared dashboard token (localStorage buddyTree.v3 / ghToken). No token or a failed write queues the call on the device (localStorage buddyTree.maildisp.queue), shows the queued state on the item, and syncs when a token appears. Nothing is ever silently dropped (per the token_gated_client_writes skill).
- Email surface (honest fallback): email buttons can't write, so in the emailed edition each disposition is (a) a deep link to the anchored item on the homepage (#item-<messageId>), where the real buttons live, and (b) specced as a pre-addressed mailto to dave@dellaquila.com (Dave sends it to himself) with subject mb-disp and body lines acct= / mid= / disp=, plus a fourth line remindOn=<YYYY-MM-DD> when disp=remind — the ingest carries it into the record (confirmed to Briefing Buddy 2026-10-30, when Dave approved adopting these links into the morning briefing email; both crons spell the carry explicitly, with a next-day default if a remind arrives without the line) — both edition crons already ingest those mails into the store at the next run, read-only. The briefing email template itself is Briefing Buddy's surface; adoption there is a separate step.
- Edition semantics (both crons updated 2026-10-30): closed (resolved / handled / was_me / not_mine) → the item never appears again, not even as FYI; open (pending / waiting) → resurfaces only with new mail, labelled with its state; remind → suppressed until remindOn, then resurfaces once with a ⏰ tag. Every item <li> must carry id/data-mid/data-acct/data-kind/data-sender/data-subject or it silently loses its buttons.
- Charter unchanged: the buttons record Dave's calls about the mail; Mail Buddy still never sends, archives, deletes, labels or marks anything.
- Verification (2026-10-30): the exact Contents-API write the page performs (GET sha → PUT base64 JSON → read back) was round-tripped against the live repo with three TEST records; the consumption logic was dry-run over fixture candidates — the resolved item was gone from the next edition's source data, a due reminder resurfaced, a pending item kept its state. Test records were removed through the same path and the store confirmed empty afterwards. Dave's own token tap can't be exercised from the VM (his token lives on his devices); the no-token queue path is the fallback he can see on any device without the token.
- Verification addendum (same day): the first publish had a real bug — the script was injected at the file's first literal </body> string, which lives inside the page's Tip Jar HTML comment, so it never executed (the buttons simply weren't there; a live browser check caught it before anything was announced). Fix (buddy-tree dd224742): script moved before the real closing </body>. Re-verified afterwards: jsdom DOM harness on the SERVED page renders 6 item holders / 20 buttons with zero script errors, and a simulated click with no token queues the correct record locally and renders the "queued on this device" chip + section note. Lesson recorded in KNOWLEDGE.md.
What this buddy has shipped and done. The review-time record — keep it fresh.
subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.+read failed on that biller message, as before; account/payment identifiers kept off the page). Spiked: a California Current newsletter, a WSJ 10-Point newsletter, an Aerostar Air Filters Veterans Day promo, and a Nextdoor Llagas digest ("I have your package!") read in full and judged not relevant — a Paradise neighbour under 5 miles away looking for a package's owner, not addressed to Emil or the house. No Clean Crawl Space, Kay Korbel, Ron, Emile or other money mail in Dad's window.subject:mb-disp newer_than:3d) found no emailed disposition calls in the last 3 days, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.+read failed on that biller message; account/payment identifiers kept off the page). Spiked: a Moss Motors clearance promo, a WSJ newsletter, and a Nextdoor Llagas digest leading with a missing-person post from the El Toro area. No Clean Crawl Space, Kay Korbel, Ron, Emile or other money mail in Dad's window.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged. The one un-dispositioned item from last evening (Wells Fargo PG&E eBill, $782.13 due Nov 25) had no new mail and was not re-listed.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.+read failed on a missing Message-ID header, so it was verified via a raw users messages get instead).subject:mb-disp newer_than:3d) found no emailed calls, so nothing was merged and dispositions.json was unchanged.+read on Dave's account) — not used; the account-scoped epoch scan is the edition's basis, and every surfaced ID was verified by a successful account-scoped read before shipping.+triage with an epoch after:/before: query returned an empty set this run; the raw users messages list with the same epoch bounds worked — the triage was cross-checked against it.+read; a subject search found nothing). It was not used. All three epoch-bounded slices were re-verified against the account-scoped (--account dave@dellaquila.com) triage, which matched exactly, and every surfaced ID was verified by a successful account-scoped read before shipping.+read on every linked account). It was not used. The run's own triage and an account-scoped re-scan of dave@dellaquila.com agree exactly (64 messages), and every surfaced ID was verified by a successful read before shipping.gmail status = connected, account dave@dellaquila.com; live triage read succeeded) — the launch condition from hire night is met.mail-attention-am (daily ~06:41 PT, next run Thu Oct 22 06:41) and mail-attention-pm (daily ~17:41 PT). Every run checks the Gmail connection first, stays honest while it's down, and is read-only.gmail status call returned empty/exit 1 in this environment, both explicit-account status calls returned connected). Dave's window: Tue Nov 17, 5:41 PM – Thu Nov 19, 5:41 PM PT (48 hours, re-covering the rate-limit-missed Nov 18 PM and Nov 19 AM editions). Light scan: people +triage --max 15, money --max 15, security/requests --max 10, one catch-all inbox triage --max 25 — 65 listings with overlap; 9 Gmail calls total in the run, inside the 14-call cap, no rate limit hit. Bulk honestly reported as capped ("at least"): all but 6 items were newsletters/promos/bulk/routine (beehiiv/Substack firehose, Black Friday promos, Schwab closing summary, Dave's own briefings/sends) or the two Nov 18 AM finds, whose bodies were read in full this run. No direct mail from Nan, Quentin, Sawyer, Amanda or the STIX team in returned results; no Chase/Wells Fargo alerts, Guidepoint requests or security alerts.Mail Buddy is Dave's inbox editor: it watches dave@dellaquila.com, ranks what needs him, and keeps a '📬 Needs your attention' list on its homepage. Read-only — it surfaces and ranks; it never sends, archives, deletes, or labels anything without Dave's explicit say-so.
Mail Buddy is Dave's inbox editor. It watches his Gmail (dave@dellaquila.com) so he doesn't have to live in it: twice a day it reads the new mail, decides what actually needs him, and publishes a short ranked list — '📬 Needs your attention' — on its homepage: who's waiting on his reply, where money is moving, which deadlines are hiding inside messages, and mail from people who matter. It is the email counterpart to Social Media Buddy's '👀 Worth your attention.' Strictly read-only: it surfaces and ranks, and never sends, archives, deletes, or labels anything without Dave's explicit say-so.
Personal Buddy (parent). Day to day it takes direction from Dave, via Astro.
Gmail is currently DISCONNECTED (verified repeatedly on 2026-10-21). Mail Buddy cannot read a single email until the connection is restored. The homepage therefore launches in an honest waiting state: the '📬 Needs your attention' section says plainly that it is waiting for the Gmail connection, with no invented or sample emails. Its first real edition is its first job the moment Gmail reconnects. Its twice-daily refresh crons (owned by its own thread, mirroring Social Media Buddy's) check the connection state first and stay honest while it is down.
Raw brain-dumps about this buddy. Each entry is timestamped; work the keepers into the dossier.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: mail-buddy-job-req-review). Please remove it from the attention list in buddies.json.
FOLLOW-UP — Dave needs more info on: "Persona + voice auditions: Inbox Editor (default) vs The Postmaster vs Night Desk Editor — Dave's pick in the main chat." (attention id: mail-buddy-auditions). Please follow up with him.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: mail-buddy-job-req-review). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Persona + voice auditions: Inbox Editor (default) vs The Postmaster vs Night Desk Editor — Dave's pick in the main chat." (attention id: mail-buddy-auditions). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: mail-buddy-job-req-review). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: mail-buddy-job-req-review). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Persona + voice auditions: Inbox Editor (default) vs The Postmaster vs Night Desk Editor — Dave's pick in the main chat." (attention id: mail-buddy-auditions). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Job req ready for review — looks good, edits, or defer?" (attention id: mail-buddy-job-req-review). Please remove it from the attention list in buddies.json.
DONE — Dave marked this done on the homepage: "Persona + voice auditions: Inbox Editor (default) vs The Postmaster vs Night Desk Editor — Dave's pick in the main chat." (attention id: mail-buddy-auditions). Please remove it from the attention list in buddies.json.
Posted as the first message in Mail Buddy's side thread at setup (2026-10-21).
Welcome aboard, Mail Buddy. 📬
You're Dave's inbox editor. Your job, from the Mail Buddy — Job Req:
Mail Buddy is Dave's inbox editor. It watches his Gmail (dave@dellaquila.com) so he doesn't have to live in it: twice a day it reads the new mail, decides what actually needs him, and publishes a short ranked list — "📬 Needs your attention" — on its homepage: who's waiting on his reply, where money is moving, which deadlines are hiding inside messages, and mail from people who matter. It is the email counterpart to Social Media Buddy's "👀 Worth your attention." Strictly read-only: it surfaces and ranks, and never sends, archives, deletes, or labels anything without Dave's explicit say-so.
Your links: - Job req: Mail Buddy — Job Req - Repo (your knowledge base — KNOWLEDGE.md, CONFIG.md, DECISIONS.md, ACCOMPLISHMENTS.md, STUDY.md, docs/ingest.md): https://github.com/davedellaquila/mail-buddy (private) - Homepage: https://davedellaquila.github.io/buddy-system/mail-buddy/ - Parent: Personal Buddy — you report through it; day to day you take direction from Dave, via Astro. - Sibling pattern: Social Media Buddy — its "👀 Worth your attention" is your design template, pointed at mail instead of feeds.
Your standard file set (already in your repo): README.md, SOUL.md, CONFIG.md, KNOWLEDGE.md, STUDY.md, DECISIONS.md, ACCOMPLISHMENTS.md, docs/job-req.md, docs/ingest.md. Keep them fresh — a stale ACCOMPLISHMENTS.md erodes trust at review time.
First jobs, in order:
1. Set up your refresh crons (owned by this thread, mirroring Social Media Buddy's): mail-attention-am (~06:41 PT) and mail-attention-pm (~17:41 PT). Every run FIRST checks the Gmail connection state.
2. Gmail is DISCONNECTED right now. Until it reconnects you cannot read a single email — so no editions, no invented lists. Your homepage already shows the honest waiting state. The moment the connection is restored, your first real "📬 Needs your attention" edition is your first job.
3. Your homepage's attention list is the morning briefing's mail source — the briefing cites it, so keep the current edition easy to reference.
Your homepage: it's live on the dashboard with the waiting state and The Desk (your repo files, rendered live, editable with Dave's token). It's the seed of your app, not a poster: design for dark AND light mode, phone/tablet/desktop widths, keep it fresh as your data changes, and link everything you mention — no mention without a path. The 🧠 brain-dump box is standard; keep it. When you outgrow the starter design, make it yours — Design Buddy is the team's taste advisor if you want a consult.
The charter, once more, because it's the whole job: read-only. Surface and rank. Never send, archive, delete, or label without Dave's explicit say-so. Honest states over tidy ones. Every item carries its why.
Mail Buddy is Dave's inbox editor. It watches his Gmail (dave@dellaquila.com) so he doesn't have to live in it: twice a day it reads the new mail, decides what actually needs him, and publishes a short ranked list — '📬 Needs your attention' — on its homepage: who's waiting on his reply, where money is moving, which deadlines are hiding inside messages, and mail from people who matter. It is the email counterpart to Social Media Buddy's '👀 Worth your attention.' Strictly read-only: it surfaces and ranks, and never sends, archives, deletes, or labels anything without Dave's explicit say-so.
Personal Buddy (parent). Day to day it takes direction from Dave, via Astro.
Gmail is currently DISCONNECTED (verified repeatedly on 2026-10-21). Mail Buddy cannot read a single email until the connection is restored. The homepage therefore launches in an honest waiting state: the '📬 Needs your attention' section says plainly that it is waiting for the Gmail connection, with no invented or sample emails. Its first real edition is its first job the moment Gmail reconnects. Its twice-daily refresh crons (owned by its own thread, mirroring Social Media Buddy's) check the connection state first and stay honest while it is down.
Dump what's on your mind about Mail 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