mixed-source-intake-routing

name	mixed-source-intake-routing
description	Route vadimgest-style multi-source intake batches into compact Obsidian notes, inbox summaries, and checkpoint updates.

Mixed-Source Intake Routing

Use this skill when processing a vadimgest / edge / backfill batch that contains multiple channels or threads (for example Telegram, Signal, WhatsApp, Gmail, meetings, dayflow, or other source dumps) and you need to turn it into durable notes.

Core rule

Process each grouped conversation or activity window as a unit. Dedupe repeated facts inside the group before writing anything.

Workflow

1. Start from the batch output. Treat the pre-run script or intake dump as the source of truth for the batch.
2. Compact by group first. If multiple raw rows belong to the same thread/channel/window, summarize them together.
3. Answer the four intake questions for each group:
   • What needs to be done?
   • How can I help now?
   • What facts changed?
   • What patterns/signals changed?
4. Route by confidence:
   • Clear entity / deal / project fact → update the right State + Log note with provenance.
   • Unclear or cross-entity signal → write one sourced Inbox note for the whole batch or group.
   • Pure noise / stale notification / service ping with no usable content → mark skipped with reason.
5. Include provenance in the note. Inbox summaries should include source line ranges or representative vadimgest://... URIs for each grouped item.
6. Commit only after writeback. If the batch provides exact checkpoint lines, update only those source positions after notes are written.
7. Verify the checkpoint. Re-read the checkpoint file (or otherwise confirm the written positions) before reporting success.

What good output looks like

• One compact note can cover several raw rows if they belong to the same conversation.
• A note can stay in Inbox when routing is still ambiguous; do not force a brittle entity guess.
• A single heartbeat/status ping should stay a short operational observation, not a task.

Pitfalls

• Do not create one note per raw row when the rows are clearly one thread.
• Do not run a broad re-read or broad commit when the batch already specifies the exact source lines to advance.
• Do not commit source lines that were not fully processed.
• Do not strip line ranges / URIs from Inbox summaries; that provenance is what makes later grooming cheap.
• Do not treat service health pings as business facts.

Verification

Before finishing, confirm:

• every non-noise group has been compacted once;
• the note path(s) are written;
• the checkpoint update matches the exact batch snippet;
• the checkpoint file now reflects the committed positions.

Support files

• references/edge-batch-example.md — a compact example from a Telegram + Signal backfill batch, including note-routing decisions and checkpoint discipline.