WF15 / Learn / Keep watch

Build a small news brief that stays current

Follow a few topics with dated sources, deduplicated stories, and a clear record of what was checked.

THE WAY THROUGH

From your material to a useful result.

01
Pick narrow topics, trusted sources, a recency window, and a maximum number of items.
02
Read the source pages; distinguish publication dates from the dates of the reported events.
03
Group multiple reports of the same event and summarize what changed without overstating certainty.
04
Keep seen-story IDs and a last-success timestamp; report stale or inaccessible sources and avoid filler on quiet days.

A FICTIONAL TASK TO PRACTICE ON

Here’s the job.

Fictional check at September 9, 2026, 08:00 UTC. Sources: S1 published September 9 reports a library opening September 8; S2 republishes the same opening; S3 published today recaps a July announcement. Window: last 48 hours. Maximum 3 items.

What a careful result should contain

1 new event: library opening on September 8, supported by S1. S2 grouped as duplicate coverage.
S3 excluded from new events because the announcement occurred in July.
The brief has one item, not three padded entries.

This is an authored reference, not a captured Grok Bot, Instinct, or other product run.

Download sample prompt Download reference

BEFORE YOU RELY ON IT

Give the result a proper check.

Every factual item has a source and relevant date.
Syndicated versions count as one story.
An old event republished today is labelled as old.

Try to break it

All sources fail to load. Pass: state the check failed. Fail: recycle yesterday’s brief as today’s news.

TAKE IT FOR A SPIN

Bring your own details.

Describe your task and paste the source material you want to use. This page prepares a prompt; your chosen AI tool does the work.

Your material and constraints

These details stay in this page until you copy them. They are not saved or sent to a model here.

Read the full starting instructions

Produce a brief for these topics using current accessible sources. Include observation time, source links, publication dates, and event dates. Deduplicate reports of the same event, respect the freshness window and item cap, and do not pad quiet days. Separate uncertainty from facts. If sources or scheduling are unavailable, say so explicitly. Never promise automatic delivery without a configured supported schedule.