Skip to content
LittleDraftDocs
Browse documentation

Context and knowledge · English documentation

Inspect context and check accuracy

See the evidence used for a reply, separate style from facts, and review important claims before sending.

2 min read · LittleDraft guide

What the context view is for

Where the reply interface offers Reply context or an evidence inspection action, open it to see the message, instructions, style hints, and reference excerpts available for that operation. For prepared replies, the view may show the saved evidence used when the draft was prepared rather than a fresh scan of your current screen.

Understand the different inputs

  • Message: The selected incoming email, accessible draft text, and available quoted conversation. This is not necessarily the complete historical thread.
  • Instructions: Your current intent and factual corrections.
  • Writing style: Habits such as greeting, phrasing, and formality. Historical style examples are not evidence of the current order or customer.
  • References: Authorized document and capture excerpts chosen for relevance.

Some sources are shortened to fit context limits. Partial-source notices and source timestamps matter: a model cannot base an answer on a paragraph that was not included.

Example: two similar tracking records

A capture contains two parcel labels for different people. The incoming message asks about order DEMO-1042. Before generating, keep the label that matches that order and recipient. Do not rely on a model to select between several nearly identical records based only on the sender’s first name.

Good direction: “Use the retained label for DEMO-1042. Include its exact parcel number. The label does not confirm collection, so don’t say it has shipped.”

What checks can and cannot establish

LittleDraft performs checks around facts, identifiers, context relevance, and Mail insertion. These reduce some errors but do not prove the reply is correct. It does not independently verify the state of your payment system, carrier account, calendar, or inventory unless the relevant evidence has actually been supplied or retrieved through the intended feature.

Instructions embedded in an incoming email, PDF, or captured screen are source content, not permission to change the app’s rules or reveal other saved information. Still inspect the output: no prompt or filter guarantees every malicious instruction or factual error will be caught.

A practical review checklist

  1. Verify the recipient and account in Mail.
  2. Compare identifiers, amounts, dates, and addresses character by character when important.
  3. Separate planned actions from completed actions. “I will check” is different from “I checked.”
  4. Look for unsupported promises about refunds, stock, delivery, or availability.
  5. Confirm any mentioned attachment is actually present.
  6. Check signatures and quoted text after insertion.

If facts are missing or conflict

Update the saved source or instruction, remove stale captures, and ask for a clarification instead of forcing a definitive answer. Private Mode can refuse an oversized context rather than silently uploading it to a cloud model. Select a shorter email or fewer references, and keep the facts needed for the answer.

Protected writing knowledge

The separate Saved Writing Knowledge view uses Touch ID or your Mac password and is read-only. It is intended for inspecting stored style information. Manage the underlying accounts and profiles in Writing style, and source documents in Library.