Source Document Links: Jump Straight to the Source

When Sera extracts a task, a decision, or a risk, a natural question follows: where did this come from? Source Document links answer it directly. Instead of trusting an extracted record on faith, you can jump straight to the exact document it was pulled from.

The Source Document field

Every Task, Decision, and Risk carries a Source Document field. It holds a direct link to the Google Doc — the meeting transcript or the notes — that the record was extracted from. Click it and you land on the origin.

This removes a tedious path. Without it, verifying a record means navigating from the record to its meeting, then to the transcript asset, then opening that document — three hops. With the Source Document link, it is one click.

Forwarded emails

Source documents are not limited to meetings. When a forwarded email references a Drive or Docs link, Sera surfaces that link as the source. So a task extracted from an emailed document points back to the document, just as a task extracted from a transcript points back to the transcript.

How review records handle it

Two record types work a little differently. The Memory Review Queue and Canon Change Requests do not use the Source Document link. Instead they carry a Source Evidence text field plus a Meeting relation. The Source Evidence field holds the specific text the extraction was based on, and the Meeting relation ties the candidate back to its meeting. This pairing gives reviewers the exact wording to check and the meeting to trace it to.

A workflow tip

The two mechanisms combine into a fast verification habit:

1. Open a record and read its Source Evidence phrase, if it has one.
2. Click through to the Source Document.
3. Use your browser's find-in-page to search for that exact phrase in the document.

You land on the precise sentence the record came from in seconds, confirming the extraction is faithful to what was actually said or written.

The same idea inside an answer

Source Document links are the record-level version of a habit that runs through the whole system. Statement-bearing records also carry their own provenance: where the claim came from, the date of that source, who asserted it, and how confident the extraction was. When you ask Sera a question, that travels with the answer, so "where does that come from?" is always a fair follow-up and always has an answer.

And when the question is about change rather than origin, ask for the record's history: "when did this due date move, and who moved it?" Notion shows a record's current values only, so its past is invisible in the interface. Sera can read the change log behind it. If nothing has been logged, she says that plainly, which is not the same as saying the record never changed.

When the field is blank, and what it covers

Two things to expect:

• The field is blank when there is no source document. A short operational email with no attachment and no Drive or Docs link has nothing to point to, so the field stays empty. That is normal, not a defect.
• It applies going forward, not retroactively. Source Document links attach to extractions made from now on. Records that were created before this behavior existed will not gain a link after the fact.

So as your memory grows, newer tasks, decisions, and risks will increasingly carry a one-click path back to their origin, while older records may still require the longer route. Over time, the ability to jump straight to the source becomes the norm — a small feature that quietly makes every extracted record trustworthy and checkable.

Key points

Tasks, Decisions, and Risks carry a Source Document field linking straight to the Google Doc — transcript or notes — they were extracted from, so you skip the meeting-to-transcript-to-open path. For forwarded emails that reference a Drive or Docs link, that link is surfaced as the source. The Memory Review Queue and Canon Change Requests instead use a Source Evidence text field plus a Meeting relation. A useful workflow is to open a record, click Source Document, then find-in-page the exact phrase from Source Evidence. The field is blank when there is no source document, such as a short email with no link, and it applies to extractions going forward rather than retroactively.