Source Emails vs. Messages: What's the Difference?

Source Emails vs. Messages: What's the Difference?

Sera writes to two email-related Notion databases, and they are not duplicates of each other. Understanding the split tells you exactly where to look for what, and it is the key to debugging anything email-related.

---

Source Emails — the raw intake log

Source Emails is created for every single email Sera receives, before any processing happens. It is her receipt and audit trail. It proves an email arrived and records what became of it.

What it holds:

• Message ID — the deduplication key. Sera checks this before doing anything. If the ID is already present, the email is skipped, which prevents double-processing even if she restarts mid-run.
• Email Type — how the email was classified.
• Processing Status — whether it is processing, processed, failed, or in manual review.
• Raw Snippet — the first 500 characters of the body, useful for spotting classification issues.
• Detected links — every URL found in the email.
• Error log — what went wrong, if anything did.

Because a Source Email record is created for every email regardless of type, this database is the complete, exhaustive intake history.

---

Messages — the semantic extraction record

Messages is created only for Operational Emails and Forwarded Threads, and only after Claude has analyzed the content. It holds the meaning of the email, not the raw intake facts.

What it holds:

• Summary — Claude's plain-language summary
• Requests — what the email asked for
• Commitments — explicit promises made
• Questions — open questions raised
• Emotional Tone — the read on the sender's tone
• Urgency — how pressing it is
• Follow-Up Needed — whether someone must act
• Sender Profile — a link to the sender's profile
• Confidentiality Level — Standard, Sensitive, or Restricted

Messages is where operational email content lives as structured, searchable knowledge.

---

Why they are not redundant

The two databases answer different questions:

• Source Emails answers: did Sera receive this email, and did she process it successfully?
• Messages answers: what did this email mean, what was committed, and who sent it?

One is about delivery and processing; the other is about meaning. You need both.

---

The debugging rule

When an email seems to be missing, always check Source Emails first:

1. Search Source Emails for the message.
2. If you find it with Status = Failed, read the error log to see what happened.
3. If there is no record at all, Sera never received the email. The problem is upstream, in delivery, not in Sera.

This single rule resolves the large majority of "where did my email go?" questions.

---

Two important special cases

Meeting emails create no Messages record. When Sera processes a meeting recording, transcript, or notes notification, she creates a Source Email record like always, but the semantic content lives in the Meeting and Meeting Asset records instead. Those serve the role that Messages plays for operational mail, so there is no Messages entry to look for.

Commitments found in Messages also become Tasks. When Claude spots an explicit promise inside an operational email, it is captured in the Messages record's Commitments field and also surfaced as a Task, so the promise does not just sit in a summary but becomes something actionable the circle can track.

---

Quick reference

• Not sure an email was processed? Go to Source Emails and check Processing Status.
• Want the summary or commitments from a thread? Go to Messages.
• Want to know who sent something? Go to Messages and follow the Sender Profile.
• Wondering whether a meeting was captured? Look at Meetings, not Source Emails.

Key points

Source Emails is the raw intake log created for every email before processing, keyed for dedup by Message ID and holding Email Type, Processing Status, a first-500-character Raw Snippet, detected links, and an error log. Messages is a semantic extraction record created only for operational emails and forwarded threads after Claude analysis, holding Summary, Requests, Commitments, Questions, Emotional Tone, Urgency, Follow-Up Needed, Sender Profile, and Confidentiality Level. The debugging rule is to check Source Emails first when an email seems missing: if the status is Failed, read the error log, and if there is no record at all, Sera never received it. Meeting emails create no Messages record because the Meeting and Meeting Asset records serve that role, and commitments found in Messages also become Tasks.