grouped-source-intake-backfill-hygiene

name	grouped-source-intake-backfill-hygiene
description	Class-level workflow for compacting grouped vadimgest/intake batches into durable Obsidian notes with Q1–Q4 routing, deduping, and checkpoint-safe backfill.

Grouped Source Intake Backfill Hygiene

Use this skill when processing a pre-grouped batch of edge/intake records from vadimgest, Telegram, Signal, Gmail, Dayflow, WhatsApp, or similar source feeds.

Core rule

Process by conversation/thread/group first, not by raw row. Deduplicate repeated facts inside the group, then decide the smallest durable home for each signal.

Workflow

1. Compact each group first.
   • Merge duplicate reminders, status pings, and repeated task markers.
   • Treat raw rows as evidence, not as note units.
2. Answer Q1–Q4 for the group.
   • Q1: What needs to be done?
   • Q2: How can I help now?
   • Q3: What facts changed?
   • Q4: What patterns/signals changed?
3. Route by confidence.
   • If the target entity/project is clear, update the relevant State/Log or topic note.
   • If routing is uncertain, write one sourced Inbox note for the group and keep the note compact.
4. Keep provenance attached.
   • Use representative vadimgest://... URIs or source line ranges in every durable note.
   • Do not invent a stronger conclusion than the evidence supports.
5. Finish with checkpoint discipline.
   • Only commit the exact listed source lines after triage/writeback for the batch.
   • Never commit sources outside the batch.

Good output shape

• One compact section per thread/group.
• One inbox note for ambiguous cross-entity batches.
• Separate entity/topic updates for clear business, deal, legal, research, or process facts.
• A short skipped/noise section for synthetic pings and boilerplate.

Pitfalls

• Do not create one note per raw message when the messages are a single conversation.
• Do not drop duplicate reminders without saying they were deduped.
• Do not over-route low-confidence chatter into entity notes.
• Do not skip checkpointing after successful writeback.

Verification

Before finishing, check that:

• each high-signal group has Q1–Q4 coverage,
• provenance is visible in the note,
• clear facts landed in the right durable home,
• noise was summarized as skipped, not silently discarded.

References

• references/edge-backfill-routing.md — session-backed example of grouped Telegram/Signal backfill, routing decisions, and checkpoint notes.