Evening routine: AI pulls every promise you made out of your inbox

I'm attaching 30 emails I sent over the past month and 10 I
received. Names and companies have been replaced with tags.

Build me a “commitment dictionary” that I'll use as the reference
for an evening routine that pulls promises out of my mail.

1. List every phrasing I use in those emails to promise something.
   For each one, note how many times it appears and whether it
   usually comes with a deadline.
2. Split them into three groups: hard commitment (clear what and
   when), soft commitment (clear what, no when), pleasantry.
3. For borderline phrasings, explain why they're borderline, and
   ask me a question that will help me decide where to put them.
4. Do the same for the emails I received: what words do people use
   to make promises to me?
5. At the end, write 10 sentences from the material that look like
   a promise but, given the context, aren't one — and explain why
   for each.

Don't add phrasings that aren't in the material. Don't generalize
from a single occurrence — if a phrase appears only once, mark it
as one-off.

Connect to my mail and go through today's sent and received
messages. Don't create anything, don't flag anything, don't save
anything anywhere — this run is read-only.

Return a table with these columns:
source (sent / received) | counterparty (name, not address) |
the sentence where you see a commitment, verbatim | type (my
commitment / their commitment / open question) | hard / soft /
uncertain | deadline, if stated | confidence (high / medium / low)

Below the table, write:
1. how many messages you went through in total, and over what
   period
2. three sentences you spent the longest deciding on, and why
3. what was missing from my rules

Always include the verbatim sentence, so I can check you didn't
make it up. When you're not sure, use “uncertain” and state why.

Here are the notes (or transcript) from a meeting:
[insert notes]

Participants and their roles: [list]. I am [name].

Pull out only commitments, nothing else. For each one, write:
- who is committed, by name; if the text doesn't make it clear,
  write “owner unclear” and quote the sentence that makes it
  impossible to tell
- what exactly they have to do, in one sentence, with a verb
- a deadline, only if one was actually stated in the notes
- the verbatim sentence from the notes the commitment comes from

Then add two short sections:
A) DECISIONS made in the meeting (not tasks — decisions)
B) OPEN ITEMS: what was discussed but not settled, noting for
   each who should be the one to decide

Don't add tasks that would logically make sense but that nobody
actually said out loud. If the meeting ended without a single
commitment, say so instead of hunting for one at any cost.

Every workday at [5:30 pm], go through my mail and today's
meetings and put together a daily summary of commitments.
Follow this exactly:

1. SCOPE
Go through messages sent and received from [today 00:00] until
now, and notes from meetings I have on today's calendar.
Skip the folders [HR, Legal, Archive], plus mailing lists, system
notifications, and auto-replies.

2. WHAT TO LOOK FOR
Using my commitment dictionary (see project rules), pull out:
a) MY PROMISES — what I promised whom today
b) PROMISES TO ME — what someone promised me today, and if the
   promise was made earlier, how long I've been waiting for it
c) AWAITING MY REPLY — messages older than [2 days] where someone
   asked me something and I didn't answer
d) UNCERTAIN — sentences you're not sure are a commitment or just
   a pleasantry

3. ACCURACY RULES
- For every item, include the verbatim sentence the commitment
  comes from, and a link to the message or notes.
- Only state a deadline if one was actually said in the text. If
  not, write “no deadline stated.” NEVER calculate or guess a
  deadline from context.
- Don't reproduce whole passages of messages. One quoted sentence
  plus a summary in your own words is enough.
- When you're not sure, put the item in UNCERTAIN instead of
  guessing.

4. FORMAT
Return the summary in this order and add nothing to it:
- one sentence about today: how many messages, how many meetings,
  how many commitments
- MY PROMISES (sorted by deadline, soonest at the top)
- PROMISES TO ME (sorted by how long I've been waiting)
- AWAITING MY REPLY
- UNCERTAIN
- one sentence: what from today is most urgent
The whole thing has to fit on one screen. If there are too many
items, shorten the descriptions, not the number of items.

5. TASK DRAFTS
For every item in the MY PROMISES and AWAITING MY REPLY sections,
create a draft task in the task manager, in the [Needs approval]
project, tagged [draft]. Don't create anything from the UNCERTAIN
section.
Never send any message, delete anything, mark anything as read,
or edit the calendar.

Change how you create task drafts from the evening summary.
Every draft must follow this shape:

TITLE: infinitive verb + what + for whom, max 60 characters.
Example: “Send price quote — Smith, ABC”

DESCRIPTION (exactly these four lines, nothing more):
Source: [source type and date, e.g. email 8/12 2:22 pm]
Verbatim: [the sentence the commitment comes from]
Deadline: [date, or “not stated”]
Link: [link to the message or notes]

DEADLINE IN THE TASK MANAGER: set it only if a deadline was
stated. If not, leave the task without a date — don't put
“today” or “tomorrow.”
Don't set PRIORITY, I decide that when approving.
TAG: [draft]. PROJECT: [Needs approval].

Never create a task from an item you flagged as uncertain.
Never create a task for something I've already done, according
to my mail.

Prepare a morning approval batch from yesterday's drafts.

List them as a numbered list, one line per item, format:
[number] [deadline or “no deadline”] [title] — [counterparty]

Below the list, give one sentence per item: why you thought it
was a commitment (a verbatim quote is enough).

Then wait for my reply in this form: numbers to confirm, numbers
to delete, numbers to edit along with what to change. For
example: “confirm 1,3,5 / delete 2 / edit 4: deadline to Friday.”

Based on that, move confirmed items to the [main] project and
remove the [draft] tag, delete the deleted ones, edit and move
the edited ones. Don't change anything else. Once done, write one
sentence about what you did, and for anything deleted, ask
whether I want to turn it into a rule in the commitment
dictionary.

Do a retrospective on our evening routine for this week. You
have access to the drafts you created, to my tasks, and to my
mail.

Return five blocks:

1. NUMBERS: how many drafts you created this week, how many I
   confirmed, edited, and deleted. For the edited ones, note what
   I most often changed (title / deadline / both).

2. FALSE ALARMS: group the deleted drafts by cause — pleasantry,
   pulled out of context, a commitment made by someone other than
   me, something I'd already done, duplicate. Give two examples
   with the verbatim sentence for each group.

3. MISSED: go through my sent mail for the week and find
   commitments I made that you didn't catch. For each one, write
   why you think it slipped through.

4. DEADLINES: was a deadline stated anywhere that wasn't actually
   in the source message? That's the most serious error — list
   it first.

5. RECOMMENDATION: three changes to the commitment dictionary or
   the routine's prompt, ranked by impact. For each, show the old
   and new wording side by side, plus the risk: what kind of real
   promise this change might cause me to miss.

Don't add rules just for the sake of it — if the same problem can
be solved by editing an existing rule, do that instead. Target
size for the dictionary is at most [one page]. Be critical of
your own work: I don't want to hear it went well, I want to know
where it's rough.

Prepare a list of exclusions for the evening routine.
Context: [role, industry, company type]. The routine reads mail
and meeting notes and creates task drafts.

Suggest which sources and content types the routine should skip
entirely. Start from these areas and add more: HR matters
(salaries, performance reviews, hiring, terminations), legal
matters and complaints, colleagues' health and personal matters,
business deals in the price-negotiation stage, addressees on my
“always manual” list.

For each item, write:
1. how to recognize that content specifically (by folder, tag,
   addressee, or meeting participants), not with a general
   description
2. whether the whole folder can be excluded, or a rule is needed
   inside the prompt
3. one false-positive situation: when it looks like sensitive
   content but is actually a routine operational message

Write the output as a list in the imperative, so I can paste it
straight into the routine's prompt.