evidence-backed-intake-backfill

name	evidence-backed-intake-backfill
description	Batch triage and writeback for evidence-fed intake slices (GitHub, Gmail, Signal, Dayflow, etc.) into Obsidian inbox or entity notes, with provenance and checkpoint discipline.

Evidence-Backed Intake Backfill

Use this skill when a pre-batched intake slice arrives from vadimgest, heartbeat, or another evidence source and you need to compact grouped records into durable notes.

Core goal

Turn raw source rows into:

1. a compact per-group Q1–Q4 summary,
2. a sourced inbox note when routing is unclear,
3. an entity/state/log note when the target is clear,
4. a verified checkpoint commit only after writeback is complete.

Workflow

1. Group first, then dedupe.

   • Compact each channel/thread group before writing anything.
   • Merge repeated facts/messages inside the group.
   • Do not create one note per raw row if the rows belong to the same conversation or repo activity window.

2. Answer the four intake questions for the group.

   • What needs to be done?
   • How can I help now?
   • What facts changed?
   • What patterns/signals changed?

3. Route the facts.

   • If the target entity is clear, write/update the relevant state/log note with provenance.
   • If routing is uncertain, too broad, or historical cross-entity context matters, create one sourced Inbox note for the batch.
   • Use representative vadimgest://... URIs and/or source line ranges in every summary.

4. Keep notes compact and sourced.

   • State facts: - **key:** value · src: source-uri · YYYY-MM-DD.
   • Log entries: ### YYYY-MM-DD - title followed by src:, mentions:, summary, facts-touched:.
   • Inbox summaries should include the grouped record count and source line ranges/URIs.

5. Commit checkpoint only after writeback.

   • Use the exact checkpoint commit snippet supplied by the batch.
   • Commit only the listed source lines.
   • If a source could not be fully processed, do not commit that source line.

Pitfalls

• Do not split one conversational thread into multiple notes unless there is a real entity boundary.
• Do not dump raw rows into notes when a compact batch summary is enough.
• Do not commit intake positions before the writeback is finished.
• Do not treat automated notifications as business facts unless they contain a real change.
• Do not comment on GitHub issues/PRs as part of intake; capture evidence only.

Verification

Before finishing, verify:

• the note path(s) written,
• the batch’s source URIs or line ranges are present,
• the checkpoint snippet was run exactly once for the committed sources,
• the final response states what was written and whether checkpointing happened.

Support files

• references/github-checkpointed-batches.md — compact runbook for grouped GitHub/evidence batches and checkpoint discipline.