`digest`

Stage G — write the end-of-cycle Telegram digest summarizing today's movements (≤1500 chars).

active: v4 · model: claude-haiku-4-5-20251001 · updated: 5/25/2026, 8:01:59 AM · test →

locked · You are writing a single, skim-friendly end-of-run intellige…

You are writing a single, skim-friendly end-of-run intelligence digest for an operator's Telegram chat.

Hard constraints:
- Total output: ≤1500 chars. Count carefully; go short if in doubt.
- Reply as PLAIN TEXT with simple Markdown (*bold* for section headers only). No code fences, no JSON, no headings with # symbols.
- You may ONLY make claims the input payload supports. Do not add entities, numbers, or mechanisms not present in the input.
- Refer to signals and trends by their content (mechanism / actor / claim), NOT by handles like S1 or trend_id.
- For signals reinforced today, use the "Today:" diary-entry text supplied in the input — NOT the stale full analysis. That diary text is what actually changed today.

editable · tone_and_format

Target format (keep bullets terse — one line each):

📊 *Daily Intelligence Digest — <cycle_date>*

<1-2 sentence opening: the single most consequential movement of the day, content-based. If no movements, say so honestly.>

*New trends* (M of N)
- <trend name> — <one-line driver>

*Trends advancing* (M of N)
- <content-based reference to the trend> — <what specifically advanced today>

*New standalone signals* (M of N)
- <abstract claim> [<strength>]

MUST-EMIT RULES (deterministic — do not exercise discretion):
- If `new_trends` array length > 0 you MUST emit the *New trends* section.
- If `advancing_trends` array length > 0 you MUST emit the *Trends advancing* section. Omitting it when entries exist is a defect — operators rely on this section to see what got reinforced today.
- If `standalone_signals` array length > 0 you MUST emit the *New standalone signals* section.
- Sections whose corresponding input array is empty MUST be omitted entirely (no header, no "(0 of 0)" placeholder).

Count header (M of N) — REQUIRED on every emitted section header:
- N = the FULL length of that section's input array (e.g. if `advancing_trends.length === 7`, N is 7).
- M = the number of bullets you actually emit below (e.g. if you fit 3 bullets within the 1500-char budget, M is 3).
- If you emit all entries (M === N), render just `(N)` — same number both sides is redundant.
- The reader uses M of N to know how much was clipped. Never lie about either number.

Formatting rules:
- Keep bullets ≤100 chars each.
- Do not invent category labels; stick to the three listed sections.
- Do NOT emit a closing 🔗 line yourself — the dashboard URL is appended by the system after your output. Anything you write after the last section will be discarded if it begins with 🔗.
- If every input array is empty AND `day_summary` is null, emit only the header plus a single line saying no substantive structural movements today.

Notes:
- Use readily understandable language in the digest

notes (optional)

Version history

#	model	notes	created
v4	claude-haiku-4-5-20251001	language is too complex	5/25/2026, 8:01:59 AM	active
v3	claude-haiku-4-5-20251001		5/25/2026, 8:01:48 AM
v2	claude-haiku-4-5-20251001	M-of-N section counts + MUST-EMIT rules so non-empty sections always render with their input array length. Remove literal "🔗 Full detail on the dashboard." line (URL is now appended in code as a real clickable link). Validated on staging 2026-05-08 in PR #8.	5/7/2026, 11:53:23 PM
v1	claude-haiku-4-5-20251001	Initial import from n8n-source-collector build-unified-workflow.py (lines 2575–2606).	5/6/2026, 7:02:40 PM