source-backed-inbox-backfill

name	source-backed-inbox-backfill
description	Compact grouped source-intake batches into durable Inbox, State, and Log notes with full provenance.

Source-backed Inbox Backfill

Use this skill when turning grouped source batches from vadimgest/intake/edge/local feeds into durable notes.

Goal

Convert raw evidence into a compact, source-backed note with the right routing, without duplicating one note per row.

Core workflow

1. Group first, then write.

   • Compact each channel/thread or conversation window before creating notes.
   • Deduplicate repeated facts inside the group.

2. Route by certainty.

   • If the entity is clear and the fact belongs to a person/org/deal/project, write/update the relevant State + Log note.
   • If routing is unclear, cross-entity, historical, or only partially grounded, write one sourced Inbox note for the batch.
   • Never fragment one grouped window into many tiny notes unless the group truly contains distinct topics.

3. Preserve provenance.

   • Include source URIs, line ranges, timestamps, or representative vadimgest://... handles.
   • For Inbox notes, make sure Q1–Q4 or equivalent summary sections reflect the grouped window.
   • Keep the source trail attached even when the batch is mostly metadata.

4. Write compact summaries.

   • Focus on what changed, what needs action, and what signal/pattern shifted.
   • If the batch is title-only, notification-only, or sparse metadata, say so explicitly instead of inventing body content.

5. Verify before checkpointing.

   • Confirm the note path is written.
   • Confirm source references are present.
   • Run the required checkpoint/commit step only after triage and writeback for the exact batch.

Pitfalls

• Do not write one note per raw row when rows belong to the same conversation.
• Do not drop source ranges when summarizing grouped evidence.
• Do not create duplicate batch notes for the same thread if an existing note already covers the active topic.
• If an edit target has repeated headings or template blocks, re-read enough context to make the insertion point unique before patching.
• If a patch collides because the file is paginated or repetitive, prefer a narrower anchor or rewrite the full section/file rather than forcing a fuzzy match.

Inbox note shape

• Title should identify the topic and date.
• Include a short source list.
• Summarize using Q1: what needs to be done, Q2: how can I help now, Q3: what facts changed, Q4: what patterns/signals changed.
• Use the Inbox as the durable fallback when the correct entity home is not obvious yet.

When to update this skill

Patch this skill when a backfill session reveals a repeatable routing rule, a provenance convention, or an editing pitfall that would apply to future source-backed intake work.

References

• references/backfill-guardrails.md — concise operating notes for grouped source backfill and paginated note edits.