Purpose + audience
Name the reader, decision, time window, and information priority.
Prompt engineering
Build versioned prompt contracts for item summaries, topic synthesis, alerts, executive briefings, and independent verification.
Prompt contract
Every template should state the job, evidence boundaries, output contract, limits, and failure behavior.
Name the reader, decision, time window, and information priority.
Label source metadata and blocks; treat embedded instructions as untrusted content.
Define field types, lengths, null behavior, uncertainty, conflict handling, and evidence IDs.
Copy the structure
A compact example for item-level summaries. Adapt the fields to the decision, not to a generic writing style.
SYSTEM / TASK
Create a neutral item record for an editorial review queue.
RULES
- Use only the enclosed source blocks.
- Return null when a date is not stated.
- Attribute claims and preserve disagreement.
- Cite evidence_ids for every key point.
OUTPUT
headline, abstract, key_points[], event_date,
content_type, open_questions[], evidence_ids[]
<SOURCE id="rss-104"> ... </SOURCE>Task separation
Extraction, item summary, cluster synthesis, briefing, alerting, and verification are different jobs.
Facts, entities, dates, content type, and evidence from one source.
Central development, new information, agreement, differences, and open questions.
Unsupported claims, mismatched dates, quantities, entities, and invalid evidence references.
Feed Signals
Versioning, examples, structured output, validation, evaluation, and production monitoring.
Create prompt templates that keep feed summaries consistent across sources, models, topics, lengths, and editorial use cases.