From 71c5bb888ae9c3de7fcc32b835e7ad592d6816c2 Mon Sep 17 00:00:00 2001 From: Jordan Burger Date: Tue, 23 Jun 2026 14:03:42 -0400 Subject: [PATCH] feat(granola): deliverable-invention gate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Upstreamed from accumulated instance experience into the granola inbound-scan (assembles into SKILL only, requires: granola): A dated commitment or deliverable extracted from a transcript needs a verbatim source quote, or it's dropped. Never attach an urgency marker ("due Friday", "committed to X", "before Y") the transcript doesn't literally contain — ship without the marker or route to the review queue. Guards two invention traps: topic conflation (don't fuse two adjacent meeting topics into one dated item) and one-off-as-standing (a single mention is not a recurring cadence). Generic rule; originating example dropped. Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 3 +++ phases/connectors/granola.md | 8 ++++++++ 2 files changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ee62a93..9011d76 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,9 @@ this project adheres to [Semantic Versioning](https://semver.org/). ## [Unreleased] +### Added +- **Granola deliverable-invention gate** (`phases/connectors/granola.md`) — a rule upstreamed from accumulated instance experience: a dated commitment or deliverable extracted from a transcript needs a **verbatim source quote** or it's dropped — never attach an urgency marker ("due Friday", "committed to X") the transcript doesn't literally contain; ship without the marker or route to the review queue. Guards two invention traps: topic conflation (don't fuse two adjacent meeting topics into one dated item) and one-off-as-standing (a single mention is not a recurring cadence). + ## [0.7.2] - 2026-06-22 diff --git a/phases/connectors/granola.md b/phases/connectors/granola.md index e3d3de2..9bf2971 100644 --- a/phases/connectors/granola.md +++ b/phases/connectors/granola.md @@ -34,6 +34,14 @@ Every action item extracted from a transcript is a **candidate** that must be ve **Never write a transcript-sourced action item directly to the action items file without cross-checking it first.** +### Deliverable-Invention Gate + +A dated commitment or deliverable pulled from a transcript needs a **verbatim source quote**, or it doesn't get written. Before attaching any urgency marker — "must be done by X", "before Y", "committed to Z", "due Friday" — to an extracted item, confirm the transcript (or a post-meeting message) contains the exact sentence stating that commitment. If the quote doesn't exist verbatim, ship the item **without** the urgency marker, or route it to `review-queue.md` for {{USER_NAME}} to confirm — never synthesize the deadline. + +Two traps that produce invented deliverables: +- **Topic conflation.** When two adjacent topics surface in the same meeting (e.g. a documentation deliverable and an unrelated upcoming trip), do not fuse them into one dated item. Write them separately and let {{USER_NAME}} cull. +- **One-off ≠ standing.** A single mention is not a recurring cadence. "Every Friday" / "every Monday" commitments must come from the speaker's own words, not be inferred from one occurrence. + ### Extraction Gate — Content, Not Breadcrumbs A "✅ transcript captured" / "notes available for [meeting]" line is **not** extraction — it is a breadcrumb that silently drops the meeting's substance. For every meeting {{USER_NAME}} attended where a transcript exists, you MUST produce the substantive extraction above (action items, decisions, commitments-by-others, deadlines, open questions) or an explicit "reviewed — no actionable content (reason)" note. A bare capture/availability breadcrumb is forbidden as the only output for an attended meeting.