grouped-source-intake-compaction

name	grouped-source-intake-compaction
description	Compact grouped vadimgest intake batches by channel/thread, preserve source provenance, and route only durable facts to Inbox or entity notes.

Grouped Source Intake Compaction

Use this skill when processing vadimgest-style intake batches that arrive grouped by source channel, thread, or conversation window.

Trigger conditions

• The batch contains multiple records from the same channel/thread.
• The records are mixed across channels or topics.
• You need to decide whether to write an Inbox note, an entity state/log note, or skip noise.
• A checkpoint/commit step is required after triage.

Core workflow

1. Compact by group first. Treat each channel/thread/window as one conversation or activity unit.
2. Deduplicate inside the group. Merge repeated facts, repeated requests, and repeated acknowledgements before writing anything.
3. Answer the four intake questions per group:
   • What needs to be done?
   • How can I help now?
   • What facts changed?
   • What patterns/signals changed?
4. Route by confidence.
   • Clear person/org/project/deal fact → update the matching entity note with source provenance.
   • Mixed, historical, or uncertain routing → write one sourced Inbox note for the whole batch or group.
   • Pure noise / acknowledgements / status pings with no durable fact → skip and count them.
5. Preserve provenance. Include representative vadimgest://... URIs or source line ranges in every summary that survives writeback.
6. Commit only after writeback. Run the exact checkpoint snippet only once triage/writeback is complete and only for the source lines listed in the batch.

What good writeback looks like

• One Inbox note can summarize multiple groups from the same batch.
• Each group has a short, evidence-backed Q1–Q4 block.
• Entity notes get only stable facts that clearly belong there.
• Social chatter, acknowledgements, and routine operational pings are usually skipped unless they change a commitment or a risk.

Pitfalls

• Do not force entity routing when the batch mixes unrelated threads or the owner is ambiguous.
• Do not write one note per raw row when the same group contains repeated or adjacent messages.
• Do not lose the source trail. If a summary has no src: line or representative URI, fix it before saving.
• Do not commit early. Checkpointing before writeback can create false progress and make reruns harder.
• Do not over-upgrade low-signal pings. Brief acknowledgements usually stay out of durable notes.

Verification

• The batch is fully covered by grouped summaries.
• All durable facts have a home: entity note, Inbox note, or explicit skip.
• Source provenance is present for every written group.
• The checkpoint file reflects only the lines actually processed.

Support files

• references/grouped-source-intake.md — compact recipe, routing heuristics, and commit hygiene for grouped batches.