name	edge-intake-writeback
description	Grouped edge/local source intake backfill into sourced inbox notes and entity notes, with exact checkpoint commit verification.

Edge intake writeback

Use this skill when draining grouped edge/local vadimgest intake batches into durable notes. It applies to Telegram, Signal, Dayflow, and similar grouped source feeds.

Core flow

Group first. Treat each channel/thread as the unit of work.
Dedupe within the group. Collapse repeated facts and repeated acknowledgements before writing anything.
Answer Q1–Q4 per group.
- What needs to be done?
- How can I help now?
- What facts changed?
- What patterns/signals changed?
Route deliberately.
- Clear entity/project/deal facts → the right State + Log note.
- Cross-entity or routing-uncertain but high-signal items → one sourced Inbox backfill note for the batch.
- Noise, system pings, and pure acknowledgements → skip with a short reason.
Keep provenance explicit. Inbox summaries must include source line ranges or representative vadimgest://... URIs for each group.
Commit only after writeback. Run the exact checkpoint snippet for the batch only after triage/writeback is complete.

Writeback format

For entity notes, prefer compact state bullets plus a dated log entry. For inbox notes, use grouped sections with:

src: or src lines:
a short summary
Q1–Q4 bullets
a skip summary for low-signal groups

Checkpointing rules

Use the exact listed commit lines for the batch.
Do not commit sources that were not fully processed.
After committing, verify the checkpoint file was updated to the expected positions.

Pitfalls

Do not write one note per raw row when multiple rows belong to the same conversation.
Do not lose provenance by summarizing without source URIs or line ranges.
Do not checkpoint before finishing all writeback for the batch.
If you only have a paginated or partial file view, re-read the exact target anchors before patching.

Verification

Re-open the created/updated note and confirm the group bullets landed correctly.
Read back the checkpoint file and confirm the committed source positions match the batch.

Reference material

references/2026-07-08-edge-backfill-example.md — worked example from a Telegram/Signal/Dayflow batch.

Edge intake writeback

Use this skill when draining grouped edge/local vadimgest intake batches into durable notes. It applies to Telegram, Signal, Dayflow, and similar grouped source feeds.

Core flow

Group first. Treat each channel/thread as the unit of work.

Dedupe within the group. Collapse repeated facts and repeated acknowledgements before writing anything.

Answer Q1–Q4 per group.

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

Route deliberately.

Clear entity/project/deal facts → the right State + Log note.
Cross-entity or routing-uncertain but high-signal items → one sourced Inbox backfill note for the batch.
Noise, system pings, and pure acknowledgements → skip with a short reason.

Keep provenance explicit. Inbox summaries must include source line ranges or representative vadimgest://... URIs for each group.

Commit only after writeback. Run the exact checkpoint snippet for the batch only after triage/writeback is complete.

Writeback format

For entity notes, prefer compact state bullets plus a dated log entry. For inbox notes, use grouped sections with:

src: or src lines:

a short summary

Q1–Q4 bullets

a skip summary for low-signal groups

Checkpointing rules

Use the exact listed commit lines for the batch.

Do not commit sources that were not fully processed.

After committing, verify the checkpoint file was updated to the expected positions.

Pitfalls

Do not write one note per raw row when multiple rows belong to the same conversation.

Do not lose provenance by summarizing without source URIs or line ranges.

Do not checkpoint before finishing all writeback for the batch.

If you only have a paginated or partial file view, re-read the exact target anchors before patching.

Verification

Re-open the created/updated note and confirm the group bullets landed correctly.

Read back the checkpoint file and confirm the committed source positions match the batch.

Reference material

references/2026-07-08-edge-backfill-example.md — worked example from a Telegram/Signal/Dayflow batch.

edge-intake-writeback