Pocket Assistant · a sample day run through the pipeline's real stages and brief format. The people and conversations are made up. ← Back to the portfolio

From three conversations to one brief

The setup: a small recorder captures the day's conversations. At 6 p.m. my desktop pulls the day's transcripts, matches each one to my calendar, files them in my notes, turns anything I committed to into a tentative calendar event, and emails me a brief written to a fixed structure. Press the button to run the sample day.

Today's recordings (Thursday)

10:02 · 14 min · matched to "Coffee w/ Dana (TechHub)"
…if you can get me the Power BI path outline by Monday, I'll slot it into the next release. And I still owe you the analytics export, I'll send that this week.
13:30 · 22 min · matched to "Supplier call: card distributor"
…we can hold the restock at that price through the 25th. Let's talk again Tuesday once you know how many decks you're building.
16:45 · 6 min · no calendar event (impromptu)
…yeah, I can take the Saturday shift at the game night. Probably. I'll confirm with my wife first.

6:00 p.m. pipeline

  1. Pull new conversations from the Pocket APIpocket.py
  2. Match each one to a calendar event by time overlapgcal.py
  3. Write a recap and action items into the Obsidian vaultvault.py
  4. Find commitments and add tentative calendar eventscommitments.md
  5. Write the brief and send it (email + phone push)digest.md · notify.py

Fridays: it tunes itself, carefully

During the week I leave short notes on recaps that missed something. On Friday night a refiner proposes edits to the prompts in skills/, then scores each proposal against a gold set of known-good cases. Nothing changes until I merge a proposal by hand.